Skip to main content
Glama

Image to Image

image_to_image

Transform an existing image by describing desired changes. Adjust the strength parameter to control how much the image is altered.

Instructions

Transform an existing image based on a text prompt. The strength parameter controls how much the image changes (0.0 = minimal change, 1.0 = maximum change). Provide the image as a URL or base64-encoded string.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nNoNumber of output images (1-6).
imageYesSource image as a URL or base64-encoded string. Max 5MB, <16MP, max 4096px per side.
modelNoModel to use.
styleNoStyle category. Not supported for V4 models.
promptYesDescription of desired changes to the image.
strengthYesChange magnitude from 0.0 (minimal) to 1.0 (maximum).
style_idNoCustom style ID.
substyleNoSubstyle to refine the style.
random_seedNoSeed for reproducibility.
image_formatNoOutput format.
negative_promptNoWhat to avoid.
Behavior2/5

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

Annotations already declare mutation (readOnlyHint=false) and open world. The description adds only minor input format hints already present in schema. No additional behavioral traits (e.g., side effects, limits) disclosed.

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

Conciseness5/5

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

Two sentences, no redundancy. Front-loaded purpose, then parameter hint. Every word serves a purpose.

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?

With 11 parameters and no output schema, the description is too minimal. It doesn't explain optional parameters (model, style) or output behavior, leaving gaps for an agent.

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 echoes some parameter info (strength, image format) but adds no new semantics beyond what's in the schema.

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 'Transform an existing image based on a text prompt,' which is a specific verb and resource. It distinguishes from siblings like generate_image (creates new) and other editing tools.

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

Usage Guidelines3/5

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

No explicit when-to-use or when-not-to-use guidance. The purpose implies use for modifying existing images, but no comparison with alternatives like generate_image or inpaint_image.

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/BartWaardenburg/recraft-mcp-server'

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