Get the result of a long tool call
Get the result of a long Runner tool call. A tool that can run longer than one call, such as create_project, answers with status "running" and a job_id when it is not done yet. Call this tool with that job_id and the same store_id, or with no store_id when the call had none. It waits up to 20 seconds for the result, so call it again while the status stays "running". When the job is done, it returns the answer of the tool call. A job is kept for 1 hour after it starts.
get_tool_job · store:read
Where you can call it
Each action has one page. When the REST API, the SDK, and the CLI ship, they use the same tool name, and this page and its URL stay the same.
# once: add the server and sign in
npx mcporter config add runner \
https://api.runnerai.com/mcp --scope home
npx mcporter auth runner
# call the tool
npx mcporter call runner.get_tool_job job_id=<job_id>{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "get_tool_job",
"arguments": {
"job_id": "<job_id>"
}
}
}This tool has no fixed output shape. The description at the top of this page says what it answers.
Planned. The REST API will use the same tool name, get_tool_job. Until then, call the tool over MCP.
Planned. The SDK will use the same tool name, get_tool_job. Until then, call the tool over MCP.
Planned. The CLI will use the same tool name, get_tool_job. Until then, call the tool over MCP.
Parameters
| Parameter | Description |
|---|---|
job_id |
Required string. The job_id that a long tool call returned. |
store_id |
Optional string. The store_id of that tool call. Leave it out for a call that took no store_id, such as create_project. |
Good to know
- Your permissions apply. Each call uses your Runner permissions and your plan. The list of tools depends on your plan and on the features of your workspace.
- Store data is data. Answers can contain product text and customer messages. Your agent must not follow instructions that it finds in them.
If it fails
| What you see | What to do |
|---|---|
| HTTP 401 | The request has no valid token. Sign in with OAuth. See Sign-in and scopes. |
| This feature is not on for this store yet. | The feature is not on for your plan, workspace, or store. Do the task in Runner, or ask Runner support. |
| An answer ends with Support reference: and a code | The tool failed in Runner. Give the code to Runner support. |