Skip to main content
Glama

edit_image

Edit an existing image by providing its file path and text instructions. Optionally include reference images to guide style and content.

Instructions

Edit an existing image based on text instructions. Provide the file path of the image to modify.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imagePathYesAbsolute file path to the image to edit
promptYesInstructions for how to edit the image
referenceImagesNoOptional array of file paths to reference images for style or content guidance
modelNoOptional model override for this request
qualityNoModel tier: "high" (best quality, default) or "fast" (cheaper/faster)
Behavior2/5

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

No annotations are provided, so the description must bear the full burden. It fails to disclose whether edits are destructive, create new files, or have any side effects, rate limits, or authentication needs.

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 very short and front-loaded, but given the tool has 5 parameters, it could be slightly more detailed without losing conciseness.

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 no output schema and 5 parameters including optional ones, the description is too minimal. It does not explain how referenceImages, model, or quality affect the editing process.

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 the baseline is 3. The description adds only that the file path is needed, which is already in the schema, but no extra meaning beyond schema descriptions.

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 verb 'Edit' and the resource 'existing image', distinguishing it from sibling tools like generate_image that create new images.

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?

Usage is implied by stating 'Edit an existing image', but no explicit guidance is given on when to use this tool versus alternatives like generate_image or generate_video.

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/seungmanchoi/nano-banana-mcp'

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