Skip to main content
Glama

Poll a job

job_status
Read-only

Track a pipeline job by ID—status, stage, per-scene progress, log tail, and final result or failure details for diagnosing render issues.

Instructions

Status, stage, per-scene progress (scenesTotal/scenesDone/currentScene — populated for probe/record/render/voice/captions/compose), log tail, and final result or error (with failure-artifact paths and, on a genuine failure, a feedbackHint pointing at the feedback tool) of a pipeline job.

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": {
      "jobId": "<jobId>"
    },
    "name": "job_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes
tailLinesNolog lines to return (default 40)

Output Schema

NameRequiredDescriptionDefault
kindYes
errorNo
jobIdYes
stageYes
resultNo
statusYes
demoDirYes
endedAtYes
logFileYes
logTailYes
startedAtYes
scenesDoneYes
scenesTotalYes
currentSceneYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.20.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedOutput schema / properties / result / propertyNames
      Added value: +{
      +  "type": "string"
      +}
  2. First observedv0.9.0

TDQS

B3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds substantive context beyond that: which job types populate the per-scene progress counters (probe/record/render/voice/captions/compose), that a log tail is included, and that failures surface artifact paths plus a feedbackHint. It never contradicts the read-only annotation, though it omits whether status is terminal vs transient (i.e. when to stop polling).

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

Conciseness3/5

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

It is a single compact sentence with no filler, but it is a run-on crammed with nested parentheses that packs return-field detail ahead of the tool's purpose. Front-loading the action ('Return the current status of a pipeline job') would have made it far easier to parse.

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

Completeness3/5

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

An output schema exists, so the lengthy enumeration of return fields is largely redundant, while the genuinely missing pieces — when to poll, when to stop, and behavior for an invalid or expired jobId — go unaddressed. For a simple 2-parameter read tool with an output schema, it is adequate but misallocates its content.

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?

Schema coverage is only 50%: tailLines carries its own description and default (40), while jobId is undocumented in the schema. The description's phrase 'log tail' loosely implies the tailLines control but adds no format or magnitude guidance, and jobId semantics (format, behavior on unknown ID) are left entirely implicit.

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

Purpose3/5

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

The sentence is a noun-phrase inventory of returned fields ('Status, stage, per-scene progress..., log tail, and final result or error') rather than a statement of what the tool does; the verb 'poll' only appears in the title. An agent can infer it reads job state, and the name job_status plus siblings job_list/job_cancel make the family obvious, but the description itself never says 'use this to check the state of a job'.

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

Usage Guidelines2/5

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

There is no guidance on when to call this versus job_list (enumerate jobs) or job_cancel (abort one), and no mention of polling cadence or what to do while status is running. The only routing hint is an internal pointer that a feedbackHint field points at the feedback tool, which concerns a returned value, not tool selection.

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