Skip to main content
Glama

ChatGPT image job status

job_status
Idempotent

Check a ChatGPT image job by ID, waiting for it to finish, or omit the ID to report bridge connectivity, queue, and recent jobs.

Instructions

Check a ChatGPT image job by job_id, waiting up to wait_seconds (default 45) for it to finish; call it again while the result says STILL RUNNING or QUEUED. Without job_id it reports the bridge itself: whether Chrome and the extension are connected, the selected ChatGPT project, the images folder, the queue and recent jobs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "job_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idNoJob id returned by generate_image or generate_sprite (e.g. img_1a2b3c4d).
wait_secondsNoReturn within this many seconds. The default 45 keeps each call under the 60-second tool limit some clients have. If the job has not finished by then, the result says STILL RUNNING or QUEUED: call job_status with its job_id again.
include_previewNoAttach the image preview when the job succeeded.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.3.0
    • changedInput schema / properties / job_id / description
      Previous value: -"Job id returned by generate_image (e.g. img_1a2b3c4d)."New value: +"Job id returned by generate_image or generate_sprite (e.g. img_1a2b3c4d)."
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: the call blocks for up to wait_seconds, returns specific status strings, and in the no-id mode surfaces bridge/Chrome connection, project, images folder, queue and recent jobs. It does not explain why readOnlyHint is false, which is the one non-obvious trait an agent might want to know.

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?

Front-loads the primary check-and-wait use, then the diagnostics mode, with no filler. The repeated mention of the default 45 seconds duplicates the schema slightly.

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?

Covers the polling loop, timeout semantics and both modes despite having no output schema to lean on. Minor gap: it does not describe what a successful result contains (asset locations, preview attachment) beyond the preview flag existing in the schema.

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%, so the schema already documents all three parameters, including the 45-second default and the job_id origin. The description largely restates that and never mentions include_preview, 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Check a ChatGPT image job by job_id') and covers a second mode ('Without job_id it reports the bridge itself'). It is distinguishable from cancel_job and generate_image by implication, but never names a sibling to sharpen the boundary.

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 explicit polling guidance — call it again while the result says STILL RUNNING or QUEUED — and explains the job_id-less mode as a diagnostics fallback. No named alternative or explicit 'do not use for X' exclusion keeps it short of a 5.

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