Skip to main content
Glama

Check a processing job

job_status

Check a Clips Kitty job's status—queued, running, done, failed, or cancelled—using its job_id.

Instructions

Where a job has got to: queued, running, done, failed or cancelled.

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

Input Schema

NameRequiredDescriptionDefault
job_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose the status state machine — genuine behavioral information beyond the schema. It omits important traits: whether states are terminal, whether unknown/expired job_ids error or return a status, latency/rate-limit behavior while polling, and whether anything besides state is returned.

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?

One compact sentence fragment, front-loaded with the payload (the state list) and free of padding. It is under-specified rather than verbose; the missing subject/verb is a minor stylistic cost given the title supplies context.

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?

For a one-parameter read tool with no annotations and no output schema, the description covers the core state space but leaves the agent without job_id provenance or any sense of the response shape beyond an enum-like status. Adequate as a minimum-viable definition, but not self-sufficient.

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

Parameters2/5

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

Schema coverage is 0% for the single parameter, so the description must compensate — and it adds nothing about job_id: no provenance, no format expectation, no invalid-ID behavior. Only one parameter exists and its name is self-evident, which keeps this from a 1, but the description provides zero added meaning.

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 states the resource (a job) and enumerates the reachable states (queued, running, done, failed, cancelled), which makes the read-satus role unambiguous even though the verb is implied rather than stated. It does not differentiate from the many sibling status tools (engine_status, publish_status, queue_status, uploadpost_status), so an agent must guess which 'job' namespace this covers.

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 explicit when-to-use statement, no mention that this is a polling tool, and no hint about where a job_id originates (e.g., from a queue/publish/schedule call). The enumerated states weakly imply a poll-until-terminal pattern, but nothing tells the agent when not to use it or what to do with a 'failed' result.

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