Skip to main content
Glama

Check Job Status

check_job_status

Check the status of a submitted deAPI job and optionally wait for completion; use it to keep polling long-running jobs instead of resubmitting an already running, paid job.

Instructions

Check status of a submitted job, optionally waiting for it to finish.

Every generation tool waits a limited time for its job. A job that takes longer (a long video, a long transcript, up to an hour) comes back with done=false and status 'processing'; call this with the job_id and wait_seconds to keep waiting, and repeat while done is false. Do not submit the job again — it is already running and paid for.

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": "check_job_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesJob request ID (UUID) to check
wait_secondsNoWait up to this many seconds for the job to finish (capped by the server, typically 45). Unset or 0: return the current status at once

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.3

TDQS

A4.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does well: it explains that generation tools only wait a limited time, that jobs can run up to an hour, and that the job is already running and paid for, which is valuable non-obvious behavior. It does not, however, describe what the wait actually blocks or what happens if the wait expires, leaving some runtime behavior implicit.

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

Conciseness4/5

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

The capability is front-loaded in the first sentence and the remaining text is a tight, purposeful explanation of the polling loop. Slight redundancy between 'comes back with done=false' and 'repeat while done is false' costs a little, but no sentence is filler.

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

Completeness5/5

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

For a two-parameter polling tool with a full schema and an output schema, the description supplies everything missing: the trigger condition, the retry loop, the cost warning against resubmission, and the realistic job duration. Nothing an agent needs to invoke it correctly is absent.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents both parameters including the server cap and the 0/unset behavior. The description adds operational meaning by tying wait_seconds to the limited wait every generation tool performs and by framing job_id as the ID from a job that already returned done=false.

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

Purpose5/5

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

The description opens with a specific verb and resource ('Check status of a submitted job') and immediately adds the optional long-poll capability. It is clearly distinct from every sibling, which are all generation/pricing tools that submit jobs rather than poll them.

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

Usage Guidelines5/5

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

It states exactly when to call it: when a generation tool returns done=false with status 'processing'. It also gives the loop pattern ('repeat while done is false') and an explicit prohibition ('Do not submit the job again'), which is the key misuse to prevent.

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