Skip to main content
Glama

generate_image

Generate an image from a model and prompt, returning the local file path and HTTP URL. Blocks until the image is ready.

Instructions

Generate one image synchronously and return the finished asset with both its local filesystem path and its HTTP URL. Blocks until the image exists. Batch generation is not supported.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nNoFixed at 1; batch generation is not supported.
seedNo
sizeNoExplicit pixel dimensions, e.g. '1920x1080'. Authoritative: a conflicting resolution or aspect_ratio is rejected.
modelYesModel ID from list_models.
promptYesPassed to the provider verbatim.
projectNoProject slug. Defaults to 'unsorted', which always exists.unsorted
qualityNo
resolutionNo
aspect_ratioNo
output_formatNo
input_reference_asset_idsNoAsset IDs previously returned by upload_asset, get_media or a generation tool, used as image references.
Behavior3/5

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

Discloses synchronous behavior and no batch support, but lacks details on side effects, auth requirements, rate limits, or failure behavior. Adequate given no annotations.

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?

Two sentences, no wasted words, front-loaded with key info.

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?

Covers essential behavioral traits and output hints (path+URL), but missing explicit return format and error handling. Good for a tool with no output schema and 11 parameters.

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 coverage is 55% (moderate), description adds overall context (synchronous, path+URL) but minimal per-parameter detail beyond schema. Adequate but does not compensate fully.

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?

Description clearly states the verb 'generate', resource 'image', and key constraints: synchronous, single image, returns filesystem path and HTTP URL. Distinguishes from siblings like generate_video.

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?

Implicitly clarifies usage: use for synchronous single image generation when immediate output needed. No explicit alternatives or when-not-to-use, but context is clear.

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/szk1234/higgshole'

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