Skip to main content
Glama
slackermafia

NanoBanana MCP Server

by slackermafia
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

Edit Image

gemini_edit_image

Edit or transform images using a text instruction. Supports single or multiple input images with control over aspect ratio and output resolution.

Instructions

Edit or transform one or more images using a text instruction, powered by the Google Gemini Nano Banana image model.

Supports single or multiple input images. Provide file paths and/or base64-encoded image data along with a text instruction.

Args:

  • prompt (string, required): A text instruction describing the edit (e.g. "Remove the background", "Combine these two images").

  • image_paths (string, optional): Comma-separated list of file paths to input images on disk. Example: "/path/to/img1.png,/path/to/img2.jpg"

  • image_base64_list (string, optional): JSON array of objects with "data" and "mimeType" fields for base64-encoded images. Example: [{"data":"base64...","mimeType":"image/png"}]

  • aspect_ratio (string, optional): Aspect ratio for the output image. Supported: 1:1, 3:2, 2:3, 3:4, 4:3, 4:5, 5:4, 9:16, 16:9, 21:9

  • model (string, optional): Gemini model ID. Defaults to "gemini-3.1-flash-image-preview".

  • output_path (string, optional): File path to save the edited image.

Returns:

  • The edited image as an embedded image block (and optionally saved to disk).

  • Any text the model returns alongside the image.

Examples:

  • prompt: "Change the car color to red" with one image

  • prompt: "Combine these two photos into a collage" with two images

  • prompt: "Apply the style of the first image to the second image" with two images

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNoGemini model ID (default: gemini-3.1-flash-image-preview)gemini-3.1-flash-image-preview
promptYesText instruction describing the desired image edit
image_sizeNoOutput image resolution: "1K" (1024px), "2K" (2048px), or "4K" (4096px)
image_pathsNoComma-separated list of file paths to input images (e.g. '/path/img1.png,/path/img2.jpg')
output_pathNoOptional file path to save the edited image
aspect_ratioNoAspect ratio for the output image. Supported: 1:1, 3:2, 2:3, 3:4, 4:3, 4:5, 5:4, 9:16, 16:9, 21:9
image_base64_listNoJSON array of objects with "data" and "mimeType" fields for base64-encoded images

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

Annotations provide limited info (openWorldHint, etc.). Description adds significant behavioral context: powered by Gemini Nano Banana model, returns an embedded image block and optional disk save, and any accompanying text. No contradiction with 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?

Well-structured with clear sections (description, args, returns, examples). Every sentence is informative, no redundancy, and it is appropriately concise for a multi-parameter tool.

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

Completeness5/5

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

Despite missing output schema, the description explains the return format. All 7 parameters are documented in schema and description adds clarifying examples. Annotations provide additional hints. Complete for this complexity level.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers all parameters (100% coverage). Description adds value with examples, format details (e.g., comma-separated paths, JSON array for base64), and supported aspect ratios, enhancing schema documentation.

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 it edits or transforms images using a text instruction. It specifies the resource (images) and action (edit/transform), distinguishing it from sibling tools like gemini_generate_image which creates 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 Guidelines4/5

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

The description provides typical usage examples and states support for single or multiple images. It implicitly tells when to use (to edit images) but lacks explicit comparison to alternatives like gemini_generate_image for creation vs editing.

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/slackermafia/NanoBanana-MCP-Server'

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