Skip to main content
Glama

Get verified Playground delivery

playground_run_delivery
Read-onlyIdempotent

Read a run’s final response and persisted canvas or media receipts, with native image previews (up to four) and original media links. Display the native image content when supported; canvasUrl is a link, not a command to open a browser. For more than four images, follow previewPage.nextOffset with previewOffset to display every page without regenerating. The verified flag is false until all required output evidence is present.

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>",
      "runId": "<runId>"
    },
    "name": "playground_run_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
runIdYesRun ID returned by preparation or execution for this project.
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.
previewOffsetNoNumber of delivery previews to skip when requesting the next preview page.

Output Schema

NameRequiredDescriptionDefault
runIdYes
statusYes
missingYes
outputsYes
partialYes
recoveryNo
verifiedYes
canvasUrlYes
deliveredYes
projectIdYes
finishedAtNo
previewPageYes
confirmationNo
missingNamesYes
requirementsYes
retryRequestNo
finalResponseYes
previewOffsetYes
creativeReviewYes
generationReviewNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real behavioral context on top: the verified flag is false until all required output evidence is present, and paging through previews does not regenerate media. It also warns that canvasUrl is inert data, preventing a plausible misread. Missing are error/partial-result behavior and what constitutes 'required output evidence,' so 4 rather than 5.

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?

Four sentences, front-loaded with what is returned, then display guidance, then pagination, then the verified flag. Every sentence carries operational information with no filler. The middle shift from display rules to pagination to flag semantics is slightly dense but still readable.

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 an output schema present, the description correctly avoids restating return shapes and instead explains the non-obvious parts: preview limits, pagination linkage, and verified-flag meaning. For a read-only, idempotent tool of this complexity that is largely sufficient. The main residual gap is what conditions produce an unverified result and whether the call fails or returns partial data.

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 baseline is 3, and the description adds meaning by linking the input previewOffset to the output field previewPage.nextOffset and by explaining the 'skip' semantics in terms of displaying every page. runId is only implicitly referenced as 'a run’s final response.' That is genuine added semantics beyond the schema, though modest.

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: 'Read a run’s final response and persisted canvas or media receipts.' It also scopes what comes back (native previews up to four, original media links, verified flag), which separates it from node/media/event siblings by scope of return rather than by naming them. It does not explicitly contrast with an alternative such as playground_run_events or playground_media_job_get, so it stops short of a 5.

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 concrete operating instructions: display native image content when supported, treat canvasUrl as a link rather than an open-browser command, and use previewOffset with previewPage.nextOffset for images beyond four. That is clear usage context for the call and its follow-ups. It offers no explicit when-not-to-use or named alternative for retrieval-type questions, which keeps it at 4.

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.