Skip to main content
Glama

edit_image

Alter a single pixel art image globally using a text description, such as adding objects or changing colors. Specify target canvas size up to 400px.

Instructions

Edit a single image globally using a text description (e.g. 'add a hat', 'change colors'). 16-400px. For editing a specific REGION use inpaint_v3 with a mask instead. For batch-editing multiple images at once use edit_images.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seedNoSeed for deterministic generation (default 0)
imageYesImage to edit
widthYesTarget canvas width (16-400px)
heightYesTarget canvas height (16-400px)
image_sizeYesCurrent image dimensions
color_imageNoColor reference image
descriptionYesEdit description
no_backgroundNoGenerate with transparent background
text_guidance_scaleNoHow closely to follow text (1.0-10.0, default 8)
Behavior3/5

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

No annotations provided, so description carries full burden. It mentions global edit and size constraints but does not describe return value, potential side effects, or authentication needs. Lacks detail for a mutation tool with no annotations.

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, zero waste. Purpose and alternatives are front-loaded. All text adds value.

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?

No output schema exits, so description should explain return value, but it doesn't. Also lacks description of color_image parameter's role. Incomplete for a tool with 9 params and nested objects.

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 baseline is 3. Description adds minimal value beyond schema—just an example and size range. Does not compensate for missing param context.

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 edits a single image globally using a text description, provides examples, and distinguishes it from sibling tools like inpaint_v3 and edit_images.

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?

Explicitly says when to use alternatives: inpaint_v3 for region edits and edit_images for batch edits, making guidance very clear.

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/rabbitcannon/pixellab-forge-mcp'

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