Skip to main content
Glama

Get job

get_job
Read-only

Current status of a generation job: queued, in_progress, completed, failed, nsfw or canceled. Completed jobs list produced assets under outputs (each with an asset id and url; also images/video as shortcuts), plus credits estimated and actually charged. job_id is the request_id returned by generate.

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

Input Schema

NameRequiredDescriptionDefault
job_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only cover readOnlyHint and openWorldHint; the description goes further by disclosing the terminal/transitional statuses and what a completed job returns (outputs with asset id and url, plus images/video shortcuts, and credits estimated vs charged). It stops short of explaining polling cadence or state-transition timing, which is the remaining behavioral gap.

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?

Front-loaded with the status enumeration, then the completion payload, then the id provenance. Three compact sentences with no filler; the parenthetical about images/video shortcuts is dense but earns its place.

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 single-parameter read tool with an output schema, this covers purpose, id provenance, and the shape of meaningful results. What is missing is guidance on repeated polling or behavior for expired/unknown job ids, but nothing essential to a correct call 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 description coverage is 0%, so the description must carry the meaning of job_id — and it does, tying it to the request_id returned by generate, which is the single most important thing an agent needs. That is meaningful semantics beyond the bare string type in 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 ("Current status of a generation job") and enumerates the full status space, so an agent knows exactly what it retrieves. It does not explicitly distinguish itself from siblings like wait_for_job or list_recent_jobs, which keeps it short of a 5.

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 implied: you call this with a job_id to inspect one job. The note that "job_id is the request_id returned by generate" is genuinely useful invocation context, but there is no guidance on when to prefer this over wait_for_job (polling) or list_recent_jobs (bulk listing).

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