Nano Banana MCP Server

text_to_image

Generate images from text prompts by creating Nano Banana tasks on RunAPI, returning task IDs, status, and output URLs.

Instructions

Create a Nano Banana task on RunAPI (text to 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", "9:16", "16:9", "3:4", "4:3", "3:2", "2:3", "5:4", "4:5", "21:9", "auto", "1:4", "1:8", "4:1", "8:1".
`callback_url`	No	Declared type: string.
`output_format`	No	Declared type: string. Known values: "png", "jpeg", "jpg".
`poll_interval_ms`	No
`output_resolution`	No	Declared type: string.
`reference_image_urls`	No	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": "9:16",
-    "type": "string"
-  },
-  {
-    "const": "16:9",
-    "type": "string"
-  },
-  {
-    "const": "3:4",
-    "type": "string"
-  },
-  {
-    "const": "4:3",
-    "type": "string"
-  },
-  {
-    "const": "3:2",
-    "type": "string"
-  },
-  {
-    "const": "2:3",
-    "type": "string"
-  },
-  {
-    "const": "5:4",
-    "type": "string"
-  },
-  {
-    "const": "4:5",
-    "type": "string"
-  },
-  {
-    "const": "21:9",
-    "type": "string"
-  },
-  {
-    "const": "auto",
-    "type": "string"
-  },
-  {
-    "const": "1:4",
-    "type": "string"
-  },
-  {
-    "const": "1:8",
-    "type": "string"
-  },
-  {
-    "const": "4:1",
-    "type": "string"
-  },
-  {
-    "const": "8:1",
-    "type": "string"
-  }
-]

addedInput schema / properties / aspect_ratio / description

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

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",
-  "nano-banana-2",
-  "nano-banana-2-lite",
-  "nano-banana-pro"
-]

removedInput schema / properties / output_format / anyOf

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

addedInput schema / properties / output_format / description

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

addedInput schema / properties / output_format / type
```
Added value: +"string"
```
addedInput schema / properties / output_resolution / description
```
Added value: +"Declared type: string."
```
addedInput schema / properties / prompt / description
```
Added value: +"Declared type: string."
```
addedInput schema / properties / reference_image_urls / description
```
Added value: +"Declared type: array."
```
addedInput schema / required
```
Added value: +[]
```

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": "9:16",
+    "type": "string"
+  },
+  {
+    "const": "16:9",
+    "type": "string"
+  },
+  {
+    "const": "3:4",
+    "type": "string"
+  },
+  {
+    "const": "4:3",
+    "type": "string"
+  },
+  {
+    "const": "3:2",
+    "type": "string"
+  },
+  {
+    "const": "2:3",
+    "type": "string"
+  },
+  {
+    "const": "5:4",
+    "type": "string"
+  },
+  {
+    "const": "4:5",
+    "type": "string"
+  },
+  {
+    "const": "21:9",
+    "type": "string"
+  },
+  {
+    "const": "auto",
+    "type": "string"
+  },
+  {
+    "const": "1:4",
+    "type": "string"
+  },
+  {
+    "const": "1:8",
+    "type": "string"
+  },
+  {
+    "const": "4:1",
+    "type": "string"
+  },
+  {
+    "const": "8:1",
+    "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",
-  "1:4",
-  "1:8",
-  "4:1",
-  "8:1"
-]

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",
-  "nano-banana-2",
-  "nano-banana-pro"
-]New value: +[
+  "nano-banana",
+  "nano-banana-2",
+  "nano-banana-2-lite",
+  "nano-banana-pro"
+]

addedInput schema / properties / output_format / anyOf

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

removedInput schema / properties / output_format / enum
```
Removed value: -[
-  "png",
-  "jpeg",
-  "jpg"
-]
```
removedInput schema / properties / output_format / type
```
Removed value: -"string"
```
removedInput schema / properties / output_resolution / enum
```
Removed value: -[
-  "1k",
-  "2k",
-  "4k"
-]
```
addedInput schema / properties / poll_interval_ms / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / prompt
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / reference_image_urls

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

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

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 are provided, so the description carries the full burden. It discloses return values (task id, status, output URLs), which is useful, but says nothing about cost/credits (despite a check_pricing sibling), auth requirements, or what the wait/poll behavior means in practice.

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, front-loaded with the action and returning the output contract. Nothing is wasted, though the vendor jargon costs a little clarity.

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 10-parameter generation tool with zero required params, no annotations, and no output schema, the description is thin. It omits cost implications, the meaning of wait/timeout/poll_interval, and callback_url semantics that an agent needs to invoke it well.

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 80%, so the schema already documents most parameters; the description adds no syntax or format detail. Baseline 3 is appropriate when the schema does the heavy lifting.

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 specific verb+resource ("Create a Nano Banana task") and disambiguates with "(text to image)", which separates it from the sibling edit_image. The jargon "Nano Banana task on RunAPI" is vendor-specific but the parenthetical makes the intent clear.

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?

No when-to-use guidance and no routing to alternatives: it never says to use edit_image for modifying an existing image or get_task to poll results. With a close sibling (edit_image) present, the absence of any differentiation is a real gap.

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

Deploy Server

text_to_image

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools