Skip to main content
Glama

generate_image

Create new images from text prompts with automatic prompt enhancement. Set aspect ratio, style, dimensions, and output format for precise control over results.

Instructions

Generate images from simple text prompts with automatic prompt enhancement for professional results.

Use this when:

  • Any image generation from text prompts

  • Need specific pixel dimensions (use targetWidth/targetHeight)

  • Professional use with precise control over all parameters

  • Quick generation with sensible defaults

NOT for:

  • Editing existing images (use edit_image instead)

  • Format conversion only (use convert_image instead)

  • Resize existing image without regeneration (use resize_image instead)

Example: "Create a hero image for a coffee shop website"

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "prompt": "<prompt>",
      "aspectRatio": "<aspectRatio>",
      "outputFormat": "<outputFormat>",
      "stripMetadata": "<stripMetadata>"
    },
    "name": "generate_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleNo
promptYes
purposeNo
qualityNo
fileNameNo
imageSizeNo
resizeFitNo
inputImageNo
aspectRatioYes1:1
blendImagesNo
targetWidthNo
outputFormatYespng
targetHeightNo
stripMetadataYes
inputImagePathNo
useGoogleSearchNo
resizeBackgroundNo
compressionPresetNo
useWorldKnowledgeNo
inputImageMimeTypeNo
showEnhancedPromptNo
skipPromptEnhancementNo
maintainCharacterConsistencyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.2

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions automatic prompt enhancement, but it does not explain side effects, file output behavior, cost, latency, rate limits, or how input images are handled.

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 well structured with a clear purpose statement, when-to-use list, exclusions, and an example. There is some redundancy and promotional phrasing such as 'professional results,' but overall it is readable and front-loaded.

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?

This is a high-complexity tool with 23 parameters, no annotations, and no output schema. The description provides good routing guidance but is not complete enough to help an agent understand most parameters or the operational behavior of generation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 23 parameters, and the description only explicitly mentions targetWidth and targetHeight. It leaves required parameters such as aspectRatio, outputFormat, and stripMetadata unexplained, so it does not compensate for the schema gap.

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 states a specific verb and resource: generating images from text prompts, with automatic prompt enhancement. It clearly distinguishes this tool from image-editing, conversion, and resizing siblings.

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

Usage Guidelines5/5

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

It explicitly lists when to use the tool and when not to use it, naming alternatives such as edit_image, convert_image, and resize_image. The routing guidance is direct and actionable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.