Skip to main content
Glama

Generate Image

generate_image

Generate AI images into the project's asset storage, for PROJECT-SPECIFIC imagery (mascots, illustrations, app icons, a particular style); generate them BEFORE building the components that use them. Returns project-relative paths (/_cdn/static/...) that resolve on the app's own domain: use them in code, or as the app icon via update_project_metadata iconUrl. An image you already hold as a file goes in with upload_asset. To edit or restyle an image, or keep a character, product or logo consistent, pass it in reference_images (this project's stored assets only: upload an outside image or the user's photo first) and say in the prompt what to change.

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>",
      "images": "<images>"
    },
    "name": "generate_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
imagesYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / images / items / properties / reference_images
      Added value: +{
      +  "description": "Up to 4 of this project's stored images (PNG/JPEG/WebP) to base the image on, by path: /_cdn/<name> or private/<name>, exactly as upload_asset, request_user_upload or generate_image returned it. Not outside URLs.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "maxItems": 4,
      +  "type": "array"
      +}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true; the description adds value beyond that by disclosing the output form (project-relative paths like /_cdn/static/... that resolve on the app's own domain) and how to consume them in code or as iconUrl. The notable gap is operational behavior: nothing says whether generation is synchronous, long-running, batch-limited, or how failures surface, despite a sibling get_job_status existing.

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?

Front-loaded with the core action and scope, then the return-value contract, then the alternatives and reference-image guidance in a logical order. It is dense but nearly every clause carries routing or behavioral information; the parenthetical examples are the only mild padding.

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?

There is no output schema, and the description compensates by explaining exactly what comes back and where the paths resolve, plus the downstream iconUrl use case. For a nested-parameter, multi-image generation tool it still omits batching limits, size options and async/timing behavior, so it is strong but not fully 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 reported at 0%, so the description must carry parameter meaning, and it does so only for reference_images: project-stored assets only, no outside URLs, and the prompt should state what to change. The images array's name, size and description fields, and the 1-4 item batching limit, are left entirely to the schema.

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?

States a specific verb and resource (generate AI images into project asset storage) and immediately scopes it to project-specific imagery with concrete examples (mascots, illustrations, app icons, a style). It explicitly separates itself from upload_asset (existing files) and update_project_metadata (iconUrl consumption), so an agent can pick it without opening any schema.

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?

Gives explicit when-to-use ('generate them BEFORE building the components that use them'), explicit routing away to upload_asset for files already held, and a conditional for editing/restyling or character consistency via reference_images. It even states the prerequisite that reference_images must be this project's stored assets, so outside images or user photos must be uploaded first.

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