Skip to main content
Glama

get_job

Fetch the current status, step count, result, and live view URL of a previously submitted browser job by UUID; call repeatedly to poll long-running jobs.

Instructions

Fetch the current state of a previously-submitted job by UUID. Returns status (queued|running|completed|failed|input_required; a cancelled job is failed with error_code CANCELLED), step count, final_result text if terminal, and the live_url of the browser's live view while it runs. Cheap — call repeatedly to poll a long-running job started by run_task.

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 UUID returned by run_task or list_jobs.
wait_secondsNoIf set (1-120), block server-side until the job reaches a terminal state or N seconds elapse.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it enumerates the status values, explains the non-obvious edge case that a cancelled job reports as failed with error_code CANCELLED, describes terminal vs running return content (final_result, live_url), and establishes that repeated polling is safe and cheap.

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 tight sentences: identity and input first, then return shape and the cancelled edge case, then the operational cost and polling guidance. No filler, and the most decision-relevant facts are front-loaded.

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?

No output schema exists, and the description compensates by spelling out the status enum, terminal results, and live_url semantics. Combined with the schema's coverage of job_id and wait_seconds, an agent has everything needed to call and interpret this tool.

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 the schema already documents both parameters, making 3 the baseline. The description reinforces where job_id comes from (run_task) but never discusses wait_seconds or the tradeoff between polling and the blocking mode, so it adds little beyond the schema.

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?

States a specific verb and resource ('Fetch the current state of a previously-submitted job') plus the lookup key (UUID), which cleanly separates it from run_task (submission) and list_jobs (enumeration). An agent can identify the tool's job without opening the schema.

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?

'Cheap — call repeatedly to poll a long-running job started by run_task' gives explicit when-to-use guidance and names the sibling that produces the job_id. It stops short of stating when not to use it or pointing to respond_to_job for the input_required state it mentions, so it is strong but not exhaustive.

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