Skip to main content
Glama

edit_image

Edit an existing image using AI. For the selected image of an existing shot use regenerate_shot_image. For a standalone image, provide the media ID and a text prompt describing what to change. Creates a new version and preserves the original. Uses Nano Banana 2.1 (google-nano-banana-2-1).

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

Input Schema

NameRequiredDescriptionDefault
modelNoImage edit model ID. Uses the default if omitted.
mediaIdYesMedia ID of the existing image to edit
editPromptYesInstructions for what to change in the image (e.g., "make the sky more orange", "add a hat to the character")
workspaceIdYesThe workspace ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose key behavior: a new version is created and the original is preserved (non-destructive), and the default model is named. It omits permissions/auth needs, failure modes, and what the response returns, which matters for a mutation tool with no annotation coverage.

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?

Four short sentences, front-loaded with the purpose, then the alternative, then the mechanics, then the model. No filler and nothing buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter mutation tool with full schema coverage and no output schema, the definition covers purpose, routing, and non-destructiveness. It could say more about what the new version returns (e.g., a new media ID), which is the main remaining gap.

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 schema already documents all four parameters. The description reinforces that mediaId points to a standalone image and that editPrompt describes the change, but adds little beyond the schema's own 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?

States a specific verb and resource (edit an existing image via AI) and immediately distinguishes itself from regenerate_shot_image by scoping this tool to standalone images. An agent can tell which tool to pick without opening either schema.

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

Usage Guidelines4/5

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

Explicitly routes shot-bound images to regenerate_shot_image and describes the standalone-image path ('provide the media ID and a text prompt'). It does not mention generate_image as the alternative for creating rather than editing, but the 'existing image' framing implies that boundary.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.