Skip to main content
Glama

Get generation status and results

get_generation
Read-onlyIdempotent

Check an existing run without starting a new one. Concept mode returns text thumbnail briefs and detailed artDirection with titles, hooks and angles, without image links or image gate verdicts. In full mode, when done, returns each option's title, hook, angle and links to its CURRENT thumbnail (the latest edit when edited), HD/4K download links, gate verdict (passed, substituted, allFlagged), informational signals, and the run config for re-runs. Links expire after 15 minutes; call again to refresh. Respect pollAfterSeconds while pending.

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

Input Schema

NameRequiredDescriptionDefault
runIdYes

Output Schema

NameRequiredDescriptionDefault
modeNo
errorNo
runIdYes
configNo
statusYes
webUrlYes
optionsNo
progressNo
projectIdYes
allFlaggedNo
packagingUrlNo
pollAfterSecondsNo
artifactExpiresAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses the 15-minute link expiry and the refresh-by-recalling workaround, the polling cadence via pollAfterSeconds, and the mode-dependent shape of results (concept mode omits image links and gate verdicts). These are non-obvious behaviors an agent could not derive from the annotations or schema.

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?

The description is front-loaded with the core purpose and then layers mode-specific return details and operational caveats in a logical order. It is dense but nearly every clause carries actionable information; the mode enumeration is slightly long given an output schema exists.

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?

For a single-parameter read tool with an output schema, the description covers the remaining gaps an agent needs: what differs between modes, link lifetime, polling behavior, and what the gate verdict values mean. Nothing required to call it correctly is missing.

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?

There is a single required parameter, runId, with 0% schema description coverage, and the description only implies its meaning through 'an existing run' without stating format or where the ID comes from. It also references 'concept mode' and 'full mode' without clarifying that mode is not a parameter of this call, which could mislead an agent into trying to pass one.

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?

The opening sentence states a specific verb and resource ('Check an existing run') and immediately contrasts it with the sibling behavior it is not ('without starting a new one'), which cleanly separates it from create_generation. The rest of the description enumerates exactly what the check returns in each mode.

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 a clear condition for use (you already have a run and want its status/results rather than a new run) and adds operational guidance to 'Respect pollAfterSeconds while pending' and to re-call after link expiry. It does not explicitly name alternatives such as show_generation_progress or list_generations, so the agent must infer which sibling to use for live progress versus a listing.

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.

Resources