Skip to main content
Glama

Check a generation

get_job
Read-onlyIdempotent

Status of one image, video or character you started (queued, running, succeeded or failed). Once an image or video succeeded: links to the result and its thumbnail that expire in an hour. Once a character is ready: its characterId. A failed job says why, and when a model's safety check refused it, which model to try instead. Poll every 10 to 20 seconds; videos usually take one to five minutes.

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

Input Schema

NameRequiredDescriptionDefault
kindYes
jobIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the read-only and idempotent annotations, the description discloses output behavior and constraints: result and thumbnail links expire in an hour, ready characters return a characterId, failures explain the cause, and safety refusals may suggest another model. It also gives polling cadence and expected video duration.

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?

The description is compact and front-loaded: it starts with what is returned, then covers success, failure, and polling guidance. Every sentence adds useful information without repetition.

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 simple polling read tool with no output schema, the description covers the status lifecycle, success payloads, expiry behavior, failure explanations, safety-refusal guidance, and polling timing. Nothing essential for correct invocation is missing.

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 must carry parameter meaning. It implies that kind selects image, video, or character and that jobId identifies the generation you started, but it never explicitly names or explains the jobId parameter's role or matching requirements.

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 states a specific verb and resource: 'Status of one image, video or character you started.' The word 'one' distinguishes it from a listing tool such as list_my_jobs, and the enumerated lifecycle states make the purpose unambiguous.

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?

It gives clear operational context: poll every 10 to 20 seconds, and videos usually take one to five minutes. It does not explicitly state when not to use it or name alternatives, so it stops short of full alternative routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources