Skip to main content
Glama

Generate Get Generation

generate_get-generation
Read-only

Retrieve a generation by ID, with wait mode to long-poll until completion and obtain the output URL directly when status is COMPLETED.

Instructions

Get a generation by id. In ChatGPT, pass wait: true and timeout: 55 for generation results instead of making repeated manual polls. When status is COMPLETED, copy the exact structuredContent.outputUrl string verbatim; signed URLs must not be reconstructed, shortened, or edited.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesJob ID
waitNoExplicitly long-poll until the generation reaches a terminal state (COMPLETED, FAILED, REJECTED) or the timeout elapses. On timeout the current state is returned with HTTP 200 - check `status` and retry. Cannot be combined with include=progress.
includeNoAdditional information to include in the response
timeoutNoMaximum seconds to block when wait=true (1-10). Default 5.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoSync generation id.
errorNo
modelNoModel used for the generation.
statusNoCurrent generation status.
errorCodeNo
outputUrlNoSigned result URL when the generation is complete. Copy this exact string verbatim; do not reconstruct, shorten, or edit it.
outputDurationNoOutput duration in seconds.
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses long-poll behavior, timeout semantics (returns current state on timeout), and instructs that outputUrl must be copied verbatim, not reconstructed. This is valuable operational detail.

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?

Three concise, front-loaded sentences: purpose, usage context, and a critical constraint. Every sentence earns its place, with no redundancy.

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?

Annotations and output schema cover safety and return values, and the description adds useful operational details. However, the contradictory timeout suggestion and lack of distinction from a sibling tool prevent it from being fully complete.

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

Parameters2/5

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

Schema covers all parameters, so baseline is 3. The description adds ChatGPT-specific parameter guidance, but it suggests `timeout: 55`, which conflicts with the schema's stated maximum of 10 seconds. This incorrect addition undermines parameter understanding.

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 clearly states 'Get a generation by id' with a specific verb and resource. However, it does not differentiate from the sibling tool 'generations_get-by-id', which likely serves the same purpose.

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?

The description provides explicit usage guidance for ChatGPT: pass `wait: true` and `timeout: 55` to avoid manual polling. It does not, however, mention alternatives or when not to use this tool, so it falls 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.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/synchronicity-labs/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server