Skip to main content
Glama

Check an ingest job

get_job
Read-onlyIdempotent

Status of an ingest job (queued, running, completed, failed). Poll every 15-30 seconds until completed. Free.

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
urlNo
nextYes
errorNo
job_idNo
resultNo
statusYes
item_idYes
qualityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / result / properties / truncated_at_seconds
      Added value: +{
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already establish readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is fully covered elsewhere. The description adds two genuinely new facts beyond those annotations: the billing model ("Free") and the polling cadence/termination condition. It stops short of describing return contents or error behavior, which keeps it at solid-but-not-rich.

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?

Three short sentences, front-loaded with what the tool returns, followed by the operational cadence and cost. No redundant restatement of the title and nothing that could be cut without losing information.

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 return values needn't be explained, and the description covers the state set, polling behavior, and cost for a simple one-parameter read tool. The only real omission is the pointing relationship to the `ingest` call that produces the job_id.

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?

One required parameter with 0% schema description coverage, so the description carries some burden; it implicitly frames job_id as an ingest job identifier and the schema supplies the `ing_...` pattern. No additional meaning (where the id comes from, what happens with an unknown or expired id) is added.

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?

Names a specific verb+resource ("status of an ingest job") and enumerates the possible states (queued, running, completed, failed), which tells an agent exactly what comes back at a high level. It does not name the `ingest` sibling as the counterpart that creates the job, so sibling differentiation is left implicit rather than stated.

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 actionable usage context: poll every 15-30 seconds and stop when the job reports completed. That is a clear operating instruction for the primary use case, though it doesn't state the precondition (call this after `ingest` returns a job_id) or what to do on failed.

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