Skip to main content
Glama

generate_image

Generate images from a text prompt with customizable quality, size, aspect ratio, and optional features like character consistency and real-world knowledge.

Instructions

Generate image with specified prompt and optional parameters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYesThe prompt for image generation (English recommended for optimal structured prompt enhancement)
purposeNoIntended use for the image (e.g., cookbook cover, social media post, presentation slide). Influences lighting, composition, and detail level to match the context.
qualityNoQuality preset controlling speed/fidelity tradeoff. Only specify when the user explicitly requests a specific quality level; omit to use the server's configured default. "fast": best for drafts and rapid iteration. "balanced": better detail and coherence, moderate latency. "quality": highest fidelity, use for final deliverables where quality matters most.
fileNameNoCustom file name for the output image. Auto-generated if not specified.
imageSizeNoImage resolution for high-quality output. Specify "1K", "2K", or "4K" when you need specific resolution. Leave unspecified for standard quality.
aspectRatioNoAspect ratio for the generated image
blendImagesNoEnable multi-image blending for combining multiple visual elements naturally. Use when prompt mentions multiple subjects or composite scenes
inputImagePathNoOptional absolute path to source image for image-to-image generation. Use when generating variations, style transfers, or similar images based on an existing image (must be an absolute path)
useGoogleSearchNoEnable Google Search grounding to access real-time web information for factually accurate image generation. Use when prompt requires current or time-sensitive data that may have changed since the model's knowledge cutoff. Leave disabled for creative, fictional, historical, or timeless content.
useWorldKnowledgeNoUse real-world knowledge for accurate context. Enable for historical figures, landmarks, or factual scenarios
maintainCharacterConsistencyNoMaintain character appearance consistency. Enable when generating same character in different poses/scenes
Behavior2/5

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

With no annotations, the description should disclose behavioral traits like cost, speed, or limitations. It only states 'generate image' without any further behavioral context (e.g., API call, content policies).

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?

The description is a single sentence, concise and free of redundancy. However, it lacks structure (e.g., bullets or sections) that could improve scannability for an 11-parameter tool.

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 the tool's complexity (11 parameters, no output schema), the description is too sparse. It does not explain return values, side effects, or how parameters interact, leaving the agent underinformed.

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 100%, so parameters are well-documented in the schema. The description adds minimal semantic value beyond restating the schema, meeting the baseline expectation.

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 clearly states the tool's action ('Generate image') and primary input ('specified prompt'), with 'optional parameters' covering the rest. No sibling tools exist, so differentiation is not needed.

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 versus alternatives. No mention of scenarios to avoid or prerequisites. The description is purely declarative without usage context.

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/shinpr/mcp-image'

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