Skip to main content
Glama

get_image_job

Retrieve an image from a generate_image call using its job_id. Waits up to wait_seconds for the generation to finish before returning the result.

Instructions

Retrieve the image from a generate_image call that returned a job_id. Waits up to wait_seconds for the generation to finish.

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_image_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesThe job_id returned by generate_image.
wait_secondsNoHow long to wait for completion, 1-45 seconds. Defaults to 30.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It usefully reveals that the call blocks for up to wait_seconds, but says nothing about what happens on timeout (error vs. partial result), whether the call is repeatable/idempotent, or whether a job can expire — all material for a job-polling tool.

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?

Two short sentences, zero filler, with the job_id dependency stated before the timing behavior. Nothing could be removed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description should describe what is actually returned — image bytes, a URL, or a status object — and what a caller sees on timeout. Those omissions matter for a retrieval tool whose only useful outcome is the returned image.

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 coverage is 100% and both parameters already document their type, range, and default, so the schema does the heavy lifting. The description restates the wait_seconds blocking semantics but adds nothing new about job_id handling, so the baseline of 3 applies.

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 gives a concrete verb and resource ("Retrieve the image") and ties it to the producing call ("from a generate_image call that returned a job_id"), which implicitly separates it from the sibling generate_image. It stops short of an explicit contrast with image_backend_status, but the purpose is 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 states a clear trigger condition: use this only after a generate_image call has returned a job_id. There are no explicit exclusions (e.g. what to do if no job_id exists, or when to prefer polling image_backend_status instead), which keeps it from a 5.

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

Deploy Server

Other Tools