Skip to main content
Glama

Create image

create_image

Generate images from text prompts, with options for model selection, size, quality, and style. Supports text-to-image, image-to-image, and image editing workflows.

Instructions

Create image Creates an image given a prompt.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nNoNumber of images to generate
seedNoSeed for deterministic-compatible image models.
sizeNoImage size. Defaults are model-specific. For gpt-image-2, omit this field or use auto for automatic sizing, or send WIDTHxHEIGHT; custom dimensions must both be multiples of 16, longest edge <= 3840px, long/short ratio <= 3:1, and total pixels between 655,360 and 8,294,400.
userNoEnd-user identifier
asyncNoReturn a task before the final image is ready when the selected model supports public async execution.
modelYesModel to use. Send this explicitly; query GET /v1/models?recommended_for=image for current recommendations.
styleNoOptional model-specific style selector. Only send when the selected model documents support for this parameter.
promptYesImage description
streamNoImage streaming is not exposed through MCP tool calls; omit stream or set it to false.
qualityNoImage quality. Defaults and accepted values are model-specific. For gpt-image-2, omit this field or use auto for automatic quality, or send low, medium, or high. Other image families may use provider-specific values.
mask_urlNoOptional mask URL for compatible image operations.
image_urlNoSingle reference image URL for compatible image-to-image models.
operationNoPublic image operation family. Reference-image models use image-to-image with image_url, image_urls, or reference_image_urls.
backgroundNoBackground handling for compatible image generation flows such as gpt-image-2 text-to-image. Not supported for gpt-image-2 image edits.
image_urlsNoReference image URLs for compatible image-to-image models.
moderationNoModeration strictness for compatible image models such as gpt-image-2
resolutionNoResolution selector for compatible image model families.
compressionNoAlias for output_compression when supported by the selected model
aspect_ratioNoAspect-ratio selector for compatible image model families.
expand_promptNoAsk compatible models to expand or enhance the prompt.
output_formatNoOutput image format for compatible image models such as gpt-image-2
negative_promptNoContent to avoid for compatible image models.
response_formatNoResponse formaturl
output_compressionNoOutput compression level from 0 to 100 for compressed formats
reference_image_urlsNoAlias used by compatible reference-image model families.
Behavior2/5

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

The description merely states 'Creates an image,' which is consistent with annotations (readOnlyHint=false), but adds no behavioral details such as async support, streaming limitations, or side effects. Annotations exist but the description still fails to provide useful context beyond the basic action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short but not concise in a helpful way; it contains a redundancy ('Create image Creates') and lacks structure. It does not earn its place by providing useful summary information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 25 parameters and no output schema, the description should provide a high-level overview of the tool's functionality and scope. Instead, it is too vague to help an agent understand the full context. The detailed schema compensates partially, but the description is incomplete.

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%, so the input schema already documents all parameters in detail. The description adds no additional meaning beyond 'given a prompt,' which is already implied by the prompt parameter. Baseline of 3 is appropriate as no extra value is provided.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description restates the tool name and title ('Create image Creates an image') without adding specificity. It does not clarify what type of image generation is performed or distinguish it from siblings like create_image_file or edit_image.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives. Sibling tools include create_image_file, edit_image, etc., but the description offers no context for selection.

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/hedging8563/tokenlab-mcp-server'

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