Skip to main content
Glama

Text To Image

text_to_image

Create images from text prompts using AI diffusion models, with controls for model, size, steps, seed and negative prompts. Returns the generated image URL.

Instructions

Generate image from text prompt using AI diffusion models.

Creates images from text descriptions. Returns the generated image URL.

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>",
      "model": "<model>"
    },
    "name": "text_to_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedNoRandom seed for reproducibility
lorasNoLoRA adapters to apply: [{'name': str, 'weight': float}]. Only for models that list them
modelYesAI model name (e.g., 'Flux1schnell', 'ZImageTurbo_INT8')
stepsNoNumber of diffusion steps. Defaults to the model's own value (see the model list); each model has its own range and some fix it
widthNoImage width in pixels. Defaults to the model's own value (see the model list)
heightNoImage height in pixels. Defaults to the model's own value (see the model list)
promptYesText description of the image you want to generate
qualityNoQuality tier for models that price by tier, e.g. 'low', 'medium', 'high' on gpt-image-1.5. Check the model card; costs vary sharply between tiers
webhook_urlNoHTTPS URL for deAPI to call when this job finishes. Notifies your own systems; the tool still returns the result here
enhance_promptNoLet the API expand the prompt before generating
guidance_scaleNoHow closely to follow the prompt. Leave unset to use the model's own default
webhook_secretNo32-255 char key deAPI signs the callback with (HMAC-SHA256). Needs webhook_url. A secret given in chat stays in the transcript
negative_promptNoThings to exclude from the image (optional)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.3

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden and does convey that output is a generated image URL and that diffusion models are used. It says nothing about cost/credit consumption, latency or job-style execution, or whether generation can fail or be moderated — all material for a paid generative operation.

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

Conciseness3/5

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

The first sentence is a well-formed, front-loaded statement of purpose. The two following sentences largely restate it ("Creates images from text descriptions" duplicates the prompt-to-image claim), so the text is short but not waste-free.

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?

An output schema exists, so return values need not be explained, and the description covers the core operation. For a 13-parameter paid generation tool with no annotations, however, it omits practical context such as credit cost, model discovery, and expected job duration.

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% across 13 parameters, so the schema already explains seed, steps, quality tiers, webhooks, and negative prompts in detail. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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

Purpose4/5

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

States a specific verb and resource ("Generate image from text prompt using AI diffusion models") and adds the return shape ("Returns the generated image URL"). It does not distinguish itself from siblings such as text_to_image_price or image_to_image, which an agent would need in order to pick correctly.

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?

There is no guidance on when to use this versus the pricing sibling, the image-to-image variant, or how to discover valid model names via get_available_models. The only conditional language ("Only for models that list them") is about a parameter, not tool selection.

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