Skip to main content
Glama

Rigged Clean

get_job

Read-only

Read an existing job by job_id. Optionally wait for a terminal state. A completed result includes the receipt and its download command.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "job_id": "<job_id>"
    },
    "name": "get_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
wait_secondsNoSeconds to wait for a terminal state. Default 45 for submission, 0 for polling.
anonymous_sessionNoKeyless session credential. Save the value returned on your first call and pass it on related calls and retries.

Output Schema

NameRequiredDescriptionDefault
idYes
tierYes
errorNo
stageNo
engineNo
job_idYes
resultNo
statusYes
billingNo
previewYes
receiptNo
download_curlNo
anonymous_sessionNoKeyless session credential. Save the value returned on your first call and pass it on related calls and retries.
processed_secondsNo
poll_after_secondsNo
full_file_price_usdNo
full_file_price_micro_usdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

readOnlyHint=true and openWorldHint=false already establish the safety profile, so the description only needs to add context. It contributes the fact that a completed result carries a receipt and a download command, but says nothing about what a non-terminal or timed-out response looks like or how wait_seconds exhaustion behaves.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the core action, then the optional wait mode, then the return payload. Nothing is redundant and no sentence could be dropped without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Annotations and an output schema carry most of the burden, and the description covers purpose, the wait option, and the shape of a completed result. It doesn't mention where job_id comes from (presumably the submission call) or the timeout fallback, minor gaps for a three-parameter read tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 67% schema coverage the schema already documents wait_seconds defaults and the anonymous_session credential, so the baseline is 3. The description reinforces job_id as the lookup key and mentions the optional wait, but adds no meaning beyond the schema and never mentions anonymous_session.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('Read an existing job by job_id') so the operation is unambiguous, and the job/receipt framing cleanly separates it from the account, upload, and media siblings. It stops short of explicitly contrasting with any sibling, which is why it isn't a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Optionally wait for a terminal state' implies the two usage modes (blocking wait after submission vs. quick poll later), but the description never states when to pick each mode or what to do if the job is still running. Usage is inferable from the schema's 'Default 45 for submission, 0 for polling' note rather than from the description itself.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources