Skip to main content
Glama

get_job

Read-onlyIdempotent

Check a job's status and Credits usage by ID without submitting work or charging Credits. Use it to confirm completion and retrieve output such as file URLs and sizes.

Instructions

Read job.status and Credits usage using its id. Pending/processing means the job is still running. Completed jobs include the original response in output. For YouTube downloads, output.results[0] contains file_url and file_size in customer storage. Private files require that storage’s access credentials; MCP does not publish them. JSON results expire after 24 hours; media retention follows the customer storage settings. Does not submit work or charge Credits. The API Key must belong to the job’s account and grant its source.

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_idYesJob ID returned by a previous asynchronous query or batch item.
response_formatNoAgent-readable presentation. MCP defaults to Markdown; json returns the original JSON text, text returns indented fields. Structured fields remain available. Does not change billing or the stored job.markdown

Output Schema

NameRequiredDescriptionDefault
jobNoJob status and metadata. Read status before using output.
codeNoMachine-readable error code when the operation fails.
chunkNoA substring of the selected document. Concatenate all chunks before parsing JSON or displaying the full document.
usageNoBilling information returned by the API.
detailNoAdditional problem detail returned by the API.
offsetNoStart position in UTF-16 code units.
outputNoOriginal response for a completed job; download results contain the customer-storage upload manifest.
messageNoError, delivery, or continuation instructions.
encodingNoHow to read the assembled chunks. Parse JSON only for json.
result_idNoTemporary result identifier. Read subsequent chunks with get_result and the same API Key.
expires_atNoUTC expiry of the temporary result.
request_idNoFlashData request identifier for support and tracing.
http_statusNoUpstream HTTP status, when an upstream request was made.
next_offsetNoNext UTF-16 position; null when the result is complete.
total_charactersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, the description discloses status semantics (pending/processing vs completed), the shape of results for YouTube downloads (output.results[0] with file_url and file_size), that private files need the customer storage's own credentials, that JSON results expire after 24 hours, and that media retention is governed by storage settings. It also states the authentication constraint that the API key must belong to the job's account and grant its source — substantial context the annotations do not carry.

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 purpose and status semantics are front-loaded in the first two sentences, with operational caveats (credentials, expiry, auth) following in a compact block. It is dense rather than padded, though the retention sentence is the weakest and adds marginal value.

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?

An output schema exists, so the description is not obligated to explain return values, yet it still flags the key output locations and the expiry/credential caveats an agent needs to act correctly. The remaining gap is the unstated relationship to get_result as an alternative retrieval path.

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 100%, so both job_id and response_format are already documented in the schema, including the enum values and the note that format does not change billing. The description adds no format or ID-syntax detail beyond that, making the baseline 3 correct.

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 opens with a specific verb and resource: "Read job.status and Credits usage using its id," so an agent knows exactly what is returned. It stops short of distinguishing itself from the sibling get_result, which plausibly covers similar retrieval territory, so sibling differentiation is missing.

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 rather than stated: "Pending/processing means the job is still running" and "Does not submit work or charge Credits" tell the agent this is a polling/read step, not a submission step. However, no alternative is named (get_result is an obvious candidate) and there is no explicit when-not guidance.

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