Skip to main content
Glama

Get a Playground media job

playground_media_job_get
Read-onlyIdempotent

Reconcile and read one media dispatch receipt by ID. Completed images include a native image preview, original media link and Playground URL; display the native image content when supported. Pass waitSeconds (up to 25) to have the server wait for the job to finish (completed, failed, or needs_reconciliation) before answering; retry_after_seconds is null once it has settled. Safe to poll after the run completes or the client disconnects.

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": {
      "projectId": "<projectId>",
      "dispatchId": "<dispatchId>"
    },
    "name": "playground_media_job_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.
dispatchIdYesDispatch receipt ID returned by generation or media_jobs_list; reuse it to check the same job.
waitSecondsNoMaximum seconds to wait for new events or a job update; prefer long polling over repeated immediate requests. Optional long poll: wait up to this many seconds (0–25, default 0) on the server for a change before returning.

Output Schema

NameRequiredDescriptionDefault
idYes
kindYes
errorYes
jobIdNo
nodeIdYes
statusYes
outputsYes
candidateYes
canvasUrlYes
createdAtNoSerialized ISO timestamp.
projectIdYes
updatedAtNoSerialized ISO timestamp.
previewPageYes
retry_after_secondsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, yet the description still adds substantive context: what completed images contain (native preview, original media link, Playground URL), the terminal statuses (completed, failed, needs_reconciliation), the null-when-settled retry_after_seconds, and post-disconnect safety. That is real behavioral disclosure beyond the structured fields.

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?

Purpose is front-loaded in the first sentence, and each following sentence carries actionable information about output and polling. The semicolon-heavy phrasing is dense but not padded.

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?

With annotations and an output schema already present, the description covers the remaining agent-facing concerns: polling strategy, terminal states, and image display. The 'reconcile' half of the stated purpose is never explained, which leaves a small gap for a tool whose name advertises reconciliation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: waitSeconds causes the server to block until a terminal state, which is a stronger statement than the schema's 'wait for new events or a job update.' This materially helps an agent choose a wait duration.

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 states a specific verb and resource: 'Reconcile and read one media dispatch receipt by ID.' The 'by ID' phrasing implicitly separates it from playground_media_jobs_list, but no sibling is named explicitly, so differentiation is left to inference.

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 gives concrete usage guidance for polling: pass waitSeconds to long-poll, and it is 'safe to poll after the run completes or the client disconnects.' It lacks an explicit statement of when to prefer playground_media_jobs_list or retry_quote over this tool, so it stops short of full alternative routing.

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.