Skip to main content
Glama

job_status

Read-only

Waits up to wait_seconds for a ComfyUI job to finish, then reports progress and status so you can poll queued or rendering work, batches, fixes, and edits.

Instructions

Waits until the job is done (up to wait_seconds, max 55) and reports progress, then returns its status. Call again while status is queued or rendering. No id = the last 10 jobs. Also takes a batch id ("batch-...", from render_batch), a fix id ("fix-...", from auto_fix) or an edit id ("edit-...").

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "job_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
wait_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare a safe, closed read-only operation, so the description adds real value on top: it is a blocking call capped at 55 seconds, it should be re-invoked on queued/rendering states, and the no-id case returns the 10 most recent jobs. What is missing is any hint about the shape of the status payload or what terminal states exist.

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?

Four short sentences, front-loaded with the blocking-wait behavior and followed by the polling rule and id semantics. Every sentence carries operational information; the phrasing is slightly dense but no sentence is filler.

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?

For a two-parameter polling tool with no output schema and read-only annotations, the description covers blocking semantics, re-invocation, identifier variants, and the no-id fallback. The remaining gap is the return payload, which the absence of an output schema leaves partly unexplained.

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 description coverage is 0%, so the description must carry the parameters, and it does: wait_seconds is described with a hard max of 55, and id is explained both by default behavior (empty = last 10 jobs) and by accepted identifier forms (job, batch-, fix-, edit-). Only the wait_seconds default value is left to the schema.

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?

States a specific verb and resource: waits for a job to finish (bounded by wait_seconds) and returns its status. The scope is precise enough that an agent knows it is a blocking status poll rather than a job listing or diagnosis, though it never names sibling tools such as diagnose_job or cancel.

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

Usage Guidelines4/5

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

Gives an explicit polling instruction: 'Call again while status is queued or rendering.' It also explains what happens with no id (returns the last 10 jobs), which is a genuine usage rule. It stops short of stating when to prefer diagnose_job or cancel over repeated polling.

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