Skip to main content
Glama

generate_image

Generate images from text prompts using AI models. Supports multiple quality tiers and customization for illustrations, photos, logos, and visuals.

Instructions

Generate an image from a text prompt — AI image generation supporting Astria, DALL-E 3, and other models. Use this for any image creation request: illustrations, photos, AI art, logos, icons, graphics, or visuals. Accepts a raw prompt and optional size, quality tier, model, and Astria-specific parameters. Quality tiers: basic (fast/cheap), standard (Nano Banana Gemini 2.5), premium (GPT Image 2.0). Use the intent-specific tools (generate_article_hero_image, etc.) when you know the content type.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYesText description of the image to generate.
sizeNoOutput image dimensions (default: 1024x1024).
qualityNoQuality tier: basic (fast/cheap), standard (Nano Banana Gemini 2.5), premium (GPT Image 2.0) (default: standard).
modelNoModel to use for image generation (default: determined by quality tier).
styleNoImage style, optional (dall-e-3 only).
astria_styleNoAstria style preset (Astria only).
color_gradingNoColor grading preset (Astria only).
film_grainNoAdd film grain effect (Astria only).
face_swapNoUse face swap with training images (Astria only).
inpaint_facesNoInpaint faces for better quality (Astria only, requires super_resolution).
face_correctNoApply face correction (Astria only).
schedulerNoScheduler algorithm (Astria only).
hires_fixNoUse high-resolution fix with super_resolution (Astria only).
controlnetNoControlNet model (Astria only).
mask_image_urlNoURL of mask image for inpainting (Astria only).
controlnet_conditioning_scaleNoControlNet conditioning scale 0.0-1.0 (Astria only).
controlnet_txt2imgNoUse ControlNet for txt2img (Astria only).
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral transparency. It lacks disclosure of side effects, error behavior, or costs beyond mentioning 'fast/cheap' for basic quality. Important details like rate limits or output format are omitted.

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 focused paragraph that front-loads the core purpose. It avoids fluff but includes a slightly redundant list of image types. Overall, it is concise enough for the complexity.

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

Completeness3/5

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

Given 17 parameters, 1 required, and no output schema, the description covers the main behavior and parameter categories. However, it lacks information on return values, error handling, and whether the operation is synchronous or asynchronous.

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 baseline is 3. The description adds limited extra context, such as explaining quality tiers and default model selection. It does not significantly enrich the meaning of individual parameters.

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 it generates an image from a text prompt, lists supported models and use cases, and explicitly distinguishes from sibling tools like generate_article_hero_image by advising when to use those alternatives.

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?

The description explains when to use this tool (any image creation request) and provides alternatives for intent-specific tools. However, it does not explicitly mention when to avoid using it or specify prerequisites like authentication.

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/Tr1ckyMag1ca1/mcp-media-engine'

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