Skip to content

Status and result tools

MCP action tools that create persisted runs return a run_id.

Use status tools to poll work and fetch results.

ToolUse it for
get_sleepwalker_visibility_run_statusPoll direct AI Visibility runs.
list_sleepwalker_visibility_runsList direct AI Visibility runs.
get_sleepwalker_content_run_statusPoll direct Content Intelligence runs.
list_sleepwalker_content_runsList direct Content Intelligence runs.
get_sleepwalker_run_resultFetch saved Console run details.
get_sleepwalker_prompt_responseFetch one AI Visibility prompt response chunk.

Required scope:

runs:read
create run
-> store run_id
-> poll status every 10 to 30 seconds
-> stop when terminal
-> fetch heavier result detail only if needed
StatusMeaning
queuedAccepted and waiting to start.
runningWork has started.
completedWork finished and result data is available.
failedWork could not complete.
cancelledWork was not run or was stopped.
partially_queuedSome requested probes were queued and some were skipped.

See Enums for shared status values.

Status tools return compact data by default.

ToolFlagUse when
get_sleepwalker_visibility_run_statusinclude_probesYou need per-probe status rows.
get_sleepwalker_visibility_run_statusinclude_resultsYou need available probe result data.
get_sleepwalker_content_run_statusinclude_resultYou need the full Content Intelligence result.

Use include flags deliberately. Large payloads are harder for MCP clients to handle.

For AI Visibility runs, fetch individual prompt responses with:

get_sleepwalker_prompt_response

Inputs:

InputTypeNotes
run_idstringRequired run ID.
result_indexintegerFetch by flattened result index.
platformstringFetch by platform.
prompt_indexintegerFetch by prompt position.
max_charsinteger1 to 25,000.
offsetintegerContinue long text from an offset.
Poll this Sleepwalker run until it completes, then summarize the result.
Fetch the first prompt response with citations for this visibility run.