Nano Banana MCP Server

edit_image

Edit images by creating a Nano Banana task on RunAPI with source image URLs and an optional prompt. Returns task ID, status, and output URLs.

Instructions

Create a Nano Banana task on RunAPI (edit image). Returns a task id, status, and output URLs.

Input Schema

TableJSON Schema

Name	Required	Description
`wait`	No	Poll until the task reaches a terminal status.
`model`	No	RunAPI model slug for this model line.
`prompt`	No	Declared type: string.
`timeout_ms`	No
`aspect_ratio`	No	Declared type: string. Known values: "1:1", "1:4", "1:8", "2:3", "3:2", "3:4", "4:1", "4:3", "4:5", "5:4", "8:1", "9:16", "16:9", "21:9", "auto".
`callback_url`	No	Declared type: string.
`output_format`	No	Declared type: string. Known values: "png", "jpeg".
`poll_interval_ms`	No
`source_image_urls`	Yes	Declared type: array.

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedv0.2.0Oct 5, 2026

addedInput schema / additionalProperties
```
Added value: +{}
```

removedInput schema / properties / aspect_ratio / anyOf

Removed value: -[
-  {
-    "const": "1:1",
-    "type": "string"
-  },
-  {
-    "const": "1:4",
-    "type": "string"
-  },
-  {
-    "const": "1:8",
-    "type": "string"
-  },
-  {
-    "const": "2:3",
-    "type": "string"
-  },
-  {
-    "const": "3:2",
-    "type": "string"
-  },
-  {
-    "const": "3:4",
-    "type": "string"
-  },
-  {
-    "const": "4:1",
-    "type": "string"
-  },
-  {
-    "const": "4:3",
-    "type": "string"
-  },
-  {
-    "const": "4:5",
-    "type": "string"
-  },
-  {
-    "const": "5:4",
-    "type": "string"
-  },
-  {
-    "const": "8:1",
-    "type": "string"
-  },
-  {
-    "const": "9:16",
-    "type": "string"
-  },
-  {
-    "const": "16:9",
-    "type": "string"
-  },
-  {
-    "const": "21:9",
-    "type": "string"
-  },
-  {
-    "const": "auto",
-    "type": "string"
-  }
-]

addedInput schema / properties / aspect_ratio / description

Added value: +"Declared type: string. Known values: \"1:1\", \"1:4\", \"1:8\", \"2:3\", \"3:2\", \"3:4\", \"4:1\", \"4:3\", \"4:5\", \"5:4\", \"8:1\", \"9:16\", \"16:9\", \"21:9\", \"auto\"."

addedInput schema / properties / aspect_ratio / type
```
Added value: +"string"
```
addedInput schema / properties / callback_url / description
```
Added value: +"Declared type: string."
```

removedInput schema / properties / model / enum

Removed value: -[
-  "nano-banana-2-lite",
-  "nano-banana-edit"
-]

removedInput schema / properties / output_format / anyOf

Removed value: -[
-  {
-    "const": "png",
-    "type": "string"
-  },
-  {
-    "const": "jpeg",
-    "type": "string"
-  }
-]

addedInput schema / properties / output_format / description

Added value: +"Declared type: string. Known values: \"png\", \"jpeg\"."

addedInput schema / properties / output_format / type
```
Added value: +"string"
```
addedInput schema / properties / prompt / description
```
Added value: +"Declared type: string."
```
removedInput schema / properties / prompt / maxLength
```
Removed value: -20000
```
removedInput schema / properties / prompt / minLength
```
Removed value: -1
```
addedInput schema / properties / source_image_urls / description
```
Added value: +"Declared type: array."
```

Changed14 schema fields changedv0.1.12Sep 14, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / aspect_ratio / anyOf

Added value: +[
+  {
+    "const": "1:1",
+    "type": "string"
+  },
+  {
+    "const": "1:4",
+    "type": "string"
+  },
+  {
+    "const": "1:8",
+    "type": "string"
+  },
+  {
+    "const": "2:3",
+    "type": "string"
+  },
+  {
+    "const": "3:2",
+    "type": "string"
+  },
+  {
+    "const": "3:4",
+    "type": "string"
+  },
+  {
+    "const": "4:1",
+    "type": "string"
+  },
+  {
+    "const": "4:3",
+    "type": "string"
+  },
+  {
+    "const": "4:5",
+    "type": "string"
+  },
+  {
+    "const": "5:4",
+    "type": "string"
+  },
+  {
+    "const": "8:1",
+    "type": "string"
+  },
+  {
+    "const": "9:16",
+    "type": "string"
+  },
+  {
+    "const": "16:9",
+    "type": "string"
+  },
+  {
+    "const": "21:9",
+    "type": "string"
+  },
+  {
+    "const": "auto",
+    "type": "string"
+  }
+]

removedInput schema / properties / aspect_ratio / enum

Removed value: -[
-  "1:1",
-  "9:16",
-  "16:9",
-  "3:4",
-  "4:3",
-  "3:2",
-  "2:3",
-  "5:4",
-  "4:5",
-  "21:9",
-  "auto"
-]

removedInput schema / properties / aspect_ratio / type
```
Removed value: -"string"
```
addedInput schema / properties / callback_url
```
Added value: +{
+  "type": "string"
+}
```

changedInput schema / properties / model / enum

Previous value: -[
-  "nano-banana-edit"
-]New value: +[
+  "nano-banana-2-lite",
+  "nano-banana-edit"
+]

addedInput schema / properties / output_format / anyOf

Added value: +[
+  {
+    "const": "png",
+    "type": "string"
+  },
+  {
+    "const": "jpeg",
+    "type": "string"
+  }
+]

removedInput schema / properties / output_format / enum
```
Removed value: -[
-  "png",
-  "jpeg"
-]
```
removedInput schema / properties / output_format / type
```
Removed value: -"string"
```
addedInput schema / properties / poll_interval_ms / maximum
```
Added value: +9007199254740991
```

addedInput schema / properties / prompt

Added value: +{
+  "maxLength": 20000,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / source_image_urls

Added value: +{
+  "items": {},
+  "type": "array"
+}

addedInput schema / properties / timeout_ms / maximum
```
Added value: +9007199254740991
```

addedInput schema / required

Added value: +[
+  "source_image_urls"
+]

First observedv0.1.0Jun 24, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden, yet it discloses only the return shape (task id, status, output URLs). It never explains the asynchronous task model, what the wait/poll_interval_ms/timeout_ms parameters do to execution, whether callback_url is needed, or any cost/auth implications.

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?

Two short sentences with no filler, and the core action plus return contract are front-loaded. It is efficient, though the brevity is part of the reason behavioral context is thin.

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 9-parameter asynchronous mutation tool with no annotations and no output schema, the description is too sparse. It names the return fields but omits polling/timeout semantics, callback behavior, and how source_image_urls drives the edit, leaving the agent under-informed.

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 description coverage is 78%, so most fields are documented in the schema, and the description adds nothing beyond them. Notably prompt, source_image_urls, timeout_ms and poll_interval_ms carry no meaningful schema description either, leaving several of the 9 parameters opaque in both places.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb and resource ("Create a ... task") and names the operation (edit image), which separates it from text_to_image by implying source-image input. The model name "Nano Banana" and platform "RunAPI" are niche identifiers, but the action is unambiguous.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no mention of the sibling text_to_image, which is the obvious alternative for image generation without a source image. An agent must infer the choice from the parenthetical "(edit image)" alone.

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

Deploy Server

edit_image

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools