Skip to main content
Glama

generate_image

DestructiveIdempotent

Create one image without a source; use derive_image for source-guided edits, upscale_image for dedicated processing, or batch_generate for multiple jobs. Preview returns requestId and preview (parameters, readiness, expiry, estimatedChargePoints); auto/run reuse that ID. Run requires user approval. Execution returns task/status and possibly nextAction; resume it after interruption, never resubmit. Retry a failed task with preview retryTaskId only.

Input Schema

NameRequiredDescriptionDefault
sizeNoGPT: pixel size e.g. 3840x2160. Others: list_models sizes.
countNoImage count; default 1, maximum 16. Zero retains the legacy default.
modelNoPublic image model ID from list_models; omit for the configured recommendation.
actionYespreview freezes inputs and quotes cost; auto checks saved spending authorization; run requires explicit user approval.
promptNoImage instructions; required for a fresh preview.
qualityNoGPT: auto (default), low, medium, high; 2.5 Sunburst/Flare also xhigh, max; affects the quote. Others: list_models qualities.
requestIdNoOriginal preview receipt for auto/run; reuse it after interruption, without re-previewing.
retryTaskIdNoFailed task ID; preview only, without replacement image parameters.
deliveryModeNonative returns previews and original links; links returns original links; metadata omits image delivery.
outputFormatNoOriginal image format; default png.
thinkingLevelNoGemini reasoning level; supported values and price multipliers come from list_models.
referenceImagesNoUp to 8 source images; preview freezes their bytes. Use derive_image for editing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / quality / description
      Previous value: -"Supported quality tier from list_models; affects the quote."New value: +"GPT: auto (default), low, medium, high; 2.5 Sunburst/Flare also xhigh, max; affects the quote. Others: list_models qualities."
    • changedInput schema / properties / size / description
      Previous value: -"Supported aspect ratio from list_models, e.g. 1:1."New value: +"GPT: pixel size e.g. 3840x2160. Others: list_models sizes."
  2. Changed13 schema fields changed
    • addedInput schema / properties / action / description
      Added value: +"preview freezes inputs and quotes cost; auto checks saved spending authorization; run requires explicit user approval."
    • addedInput schema / properties / count / description
      Added value: +"Image count; default 1, maximum 16. Zero retains the legacy default."
    • addedInput schema / properties / deliveryMode / description
      Added value: +"native returns previews and original links; links returns original links; metadata omits image delivery."
    • addedInput schema / properties / model / description
      Added value: +"Public image model ID from list_models; omit for the configured recommendation."
    • addedInput schema / properties / outputFormat / description
      Added value: +"Original image format; default png."
    • addedInput schema / properties / prompt / description
      Added value: +"Image instructions; required for a fresh preview."
    • addedInput schema / properties / quality / description
      Added value: +"Supported quality tier from list_models; affects the quote."
    • changedInput schema / properties / referenceImages / description
      Previous value: -"URL/data URL."New value: +"Up to 8 source images; preview freezes their bytes. Use derive_image for editing."
    • addedInput schema / properties / referenceImages / items / description
      Added value: +"Public image URL or image data URL."
    • addedInput schema / properties / requestId / description
      Added value: +"Original preview receipt for auto/run; reuse it after interruption, without re-previewing."
    • addedInput schema / properties / retryTaskId / description
      Added value: +"Failed task ID; preview only, without replacement image parameters."
    • changedInput schema / properties / size / description
      Previous value: -"Ratio."New value: +"Supported aspect ratio from list_models, e.g. 1:1."
    • changedInput schema / properties / thinkingLevel / description
      Previous value: -"Gemini thinking; extended=高级模式."New value: +"Gemini reasoning level; supported values and price multipliers come from list_models."
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The annotations already declare non-read-only, idempotent, and destructive behavior. The description adds meaningful context beyond them: previews quote estimatedChargePoints, run requires user approval, interrupted tasks should be resumed rather than resubmitted, and failed tasks are retried only through retryTaskId.

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?

The description is dense but front-loaded with purpose and alternatives before the workflow details. Every sentence adds operational value for a complex 12-parameter tool, with no redundant filler.

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?

For a complex generation tool with no output schema, the description covers the main lifecycle, return signals, approval, and retry semantics well. It could more explicitly mention generation_status or wait_images for polling, but the essential calling behavior is complete.

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 description coverage is 100%, and the schema already documents action, requestId, retryTaskId, and most parameters in detail. The description reinforces the requestId/retry workflow but adds little parameter meaning beyond the schema and does not discuss many fields such as size, count, model, or quality.

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 description states a specific verb, resource, and scope: 'Create one image without a source.' It immediately distinguishes the tool from derive_image, upscale_image, and batch_generate, so an agent can identify the correct sibling without inspecting schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit routing guidance for source-guided edits, dedicated processing, and multiple jobs. It also explains the preview/auto/run lifecycle, approval requirement, interruption resume behavior, and retry path, leaving little to inference.

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