Skip to main content
Glama

edit_image

Modify existing images using natural language instructions to add, remove, or change elements, backgrounds, and styles, or to enhance and retouch photos.

Instructions

Edit existing images using natural language instructions.

Use this when:

  • Modifying an existing image

  • Adding or removing elements from a photo

  • Changing backgrounds or styles

  • Enhancing or retouching images

NOT for:

  • Creating new images from scratch (use generate_image instead)

  • Format conversion without AI changes (use convert_image instead)

Example: "Remove the background from this product photo"

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": {
      "editPrompt": "<editPrompt>",
      "preserveStyle": "<preserveStyle>"
    },
    "name": "edit_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNameNo
editPromptYes
inputImageNo
aspectRatioNo
preserveStyleYes
inputImagePathNo
inputImageMimeTypeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.2

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about cost/latency of an AI edit, whether the source image is overwritten or a new asset is returned, or what the caller receives back. The example clarifies intent but adds no operational context. The one disclosed trait — that edits are driven by natural language — is already implied by the required editPrompt parameter.

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?

Front-loaded one-line purpose followed by scannable when/when-not bullets and a single concrete example. No filler sentences, and the exclusion list is placed where an agent scanning for routing decisions will find it.

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?

For a 7-parameter AI mutation tool with no annotations and no output schema, the definition covers routing well but leaves behavioral and parameter behavior largely unexplained. An agent still cannot determine which image-input parameter to populate or what happens to the original file.

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 7 parameters, so the description must compensate and does not. Most critically it never explains the relationship between inputImage, inputImagePath, and fileName — three overlapping ways to specify the source — nor what preserveStyle (required, default true) or aspectRatio actually control. Only editPrompt receives indirect clarification via the example.

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?

States a specific verb+resource ("Edit existing images") and a specific mechanism ("natural language instructions"). It explicitly separates itself from generate_image and convert_image, so an agent can select it without opening a sibling schema.

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?

Provides an explicit 'Use this when' list of four scenarios and a 'NOT for' section naming two concrete alternatives with the condition that selects each. This is the strongest possible routing guidance.

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