Skip to main content
Glama

job_status

Read-only

Check import, analyze, render, or QA job status and optionally wait for completion; finished QA jobs return contact sheets and cut-frame images.

Instructions

Status of one or more jobs (import, analyze, render, qa). Waits up to wait seconds for them to finish. A finished qa job includes its contact sheet and cut frames as images.

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

Input Schema

NameRequiredDescriptionDefault
waitNo
jobIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds real value beyond that by disclosing long-poll semantics ('waits up to `wait` seconds') and that a finished qa job returns contact sheet and cut frames as images, but it never states what happens on timeout (pending status? partial results?) or how unknown job IDs are handled.

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, zero filler, with the core purpose front-loaded and the wait behavior and qa-specific return content following in priority order.

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?

With no output schema and no schema descriptions, the description should say more about the returned status shape (status values, per-job results, timeout behavior). It does cover the qa image payload, which is the most surprising return case, but leaves the general response contract unstated.

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 description coverage is 0%, so the description carries the burden. It explains the `wait` parameter's meaning (seconds to block for completion) but says nothing about `jobIds` beyond 'one or more jobs' – no mention of the 20-item cap or accepted ID format. Partial compensation only.

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?

The description opens with a specific verb+resource ('Status of one or more jobs') and enumerates the job types it covers (import, analyze, render, qa), which lets an agent separate it from job_cancel and render_start. It stops short of naming a sibling to route against, so it is clear but not fully differentiated.

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?

Usage is only implied: an agent must infer that this is the polling tool to call after kicking off an import/analyze/render/qa job. There is no explicit when-to-use vs. job_cancel, nor any guidance on what to do if the jobs have not finished within the wait window.

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