Skip to main content
Glama

Generate an image

generate_image

Generate an image from a prompt. With references, the image model also sees up to 3 pictures: image assets, frames or contact sheets of video assets, and frames or contact sheets of the edit. Use them to keep a person's face from a frame, to copy the style of an image, or to sum up a range of a video or of the edit in one picture. Choose aspectRatio and imageSize (1K is standard). It answers at once with a Job ID and the media is made in the background: start every generation you need, keep working, then call wait_for_jobs with all their Job IDs to get each Asset ID for patch_film. One image uses 26 credits at 1K, 38 at 2K and 57 at 4K, with or without references.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYesUp to 4000 characters.
imageSizeYes
projectIdYesThe project this call runs on without changing the open project. null (or leaving it out) uses the open project. wait_for_jobs takes the projectId of the calls that started the jobs.
referencesYesUp to 3 pictures the image model sees with the prompt, in this order, or [] to generate from the prompt alone. Each one is: asset:ID, an image asset as it is (a video asset with no time gives its first frame); asset:ID#t=14.6, the frame of a video asset at 14.6 seconds; asset:ID#t=200,215, a contact sheet of that video from 200 to 215 seconds; film:#t=3.2, the frame of the edit at 3.2 seconds; film:#t=0,12, a contact sheet of the edit from 0 to 12 seconds. Contact sheets have no times written on them. Use the IDs search_assets gives. In the prompt, say what to take from each picture by its place: "keep the face of the man in the first picture", "paint it in the style of the second picture", "one poster that sums up the scene in the third picture".
aspectRatioYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With annotations only covering readOnly/openWorld/idempotent/destructive flags, the description adds substantial behavioral context: the call returns a Job ID immediately while media is produced asynchronously, credit costs vary by size (26/38/57 at 1K/2K/4K), and cost is independent of references. This is exactly the kind of async, cost, and follow-up behavior an agent needs and cannot get from the annotations.

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 purpose, then references usage, then async workflow, then cost. Every sentence carries information, though the references and cost sentences are dense and the description runs long for a single tool; nothing is wasted but it is not maximally tight.

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?

No output schema exists, yet the description explains the return (Job ID), how to resolve it (wait_for_jobs -> Asset ID), and the downstream consumer (patch_film). Combined with cost and reference semantics, an agent has everything needed to invoke and follow through correctly.

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 60%; the description adds meaning to imageSize by tying each enum value to a credit cost and flagging 1K as standard, and reinforces that references take up to 3 ordered pictures. The prompt and projectId semantics are carried by the schema, and aspectRatio values get no added explanation beyond the enum, so it is not a full 5.

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 an image from a prompt') and immediately scopes the resource further by explaining the references input. It is trivially distinguishable from siblings like generate_video, generate_music, or generate_speech, and the reference types (image assets, frames, contact sheets) make the tool's domain concrete.

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 explicit usage context for references ('keep a person's face', 'copy the style', 'sum up a range') and a full workflow: start generations, keep working, then call wait_for_jobs with the Job IDs to get Asset IDs for patch_film. It does not state when not to use this tool versus alternatives (e.g. generate_video), so it stops 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.