imagen-4-mcp

text_to_image

Create Imagen 4 image-generation tasks from text prompts on RunAPI and return task IDs, status, and output URLs.

Instructions

Create a Imagen 4 task on RunAPI (text to image). Returns a task id, status, and output URLs.

Input Schema

Name	Required	Description
`seed`	No	Declared type: integer.
`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", "16:9", "9:16", "3:4", "4:3", "auto".
`callback_url`	No	Declared type: string.
`negative_prompt`	No	Declared type: string.
`poll_interval_ms`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedv0.2.0Oct 5, 2026
- changedInput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```
- addedInput schema / properties / aspect_ratio / description
```
Added value: +"Declared type: string. Known values: \"1:1\", \"16:9\", \"9:16\", \"3:4\", \"4:3\", \"auto\"."
```
- removedInput schema / properties / aspect_ratio / enum
```
Removed value: -[
-  "1:1",
-  "16:9",
-  "9:16",
-  "3:4",
-  "4:3",
-  "auto"
-]
```
- addedInput schema / properties / callback_url / description
```
Added value: +"Declared type: string."
```
- removedInput schema / properties / model / enum
```
Removed value: -[
-  "imagen-4",
-  "imagen-4-fast",
-  "imagen-4-ultra"
-]
```
- addedInput schema / properties / negative_prompt / description
```
Added value: +"Declared type: string."
```
- addedInput schema / properties / poll_interval_ms / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / prompt / description
```
Added value: +"Declared type: string."
```
- addedInput schema / properties / seed / description
```
Added value: +"Declared type: integer."
```
- changedInput schema / properties / seed / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / timeout_ms / maximum
```
Added value: +9007199254740991
```
- addedInput schema / required
```
Added value: +[]
```

Changed6 schema fields changedv0.1.7Jul 13, 2026

changedInput schema / properties / aspect_ratio / enum

Previous value: -[
-  "1:1",
-  "16:9",
-  "9:16",
-  "3:4",
-  "4:3"
-]New value: +[
+  "1:1",
+  "16:9",
+  "9:16",
+  "3:4",
+  "4:3",
+  "auto"
+]

addedInput schema / properties / callback_url
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / negative_prompt
```
Added value: +{
+  "type": "string"
+}
```

removedInput schema / properties / output_count

Removed value: -{
-  "enum": [
-    1,
-    2,
-    3,
-    4
-  ],
-  "type": "number"
-}

addedInput schema / properties / prompt
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / seed
```
Added value: +{
+  "type": "number"
+}
```

First observedv0.1.0Jun 24, 2026

TDQS

C2.9/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the return payload (task id, status, output URLs), which is genuinely useful given there is no output schema, but it omits auth/permission needs, rate limits, and the asynchronous task semantics implied by the wait and poll_interval_ms parameters.

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 tight sentences with the core action front-loaded and the return shape second; there is no filler. Minor grammar slip ('a Imagen 4 task') but structure is efficient.

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 generation tool with no annotations and no output schema, the description is far too thin: it never explains the wait/polling model, the role of the prompt, or any constraints, leaving the agent unable to call it confidently.

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

Parameters2/5

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

Nine parameters and the description says nothing about any of them. The 78% schema coverage is misleading because most schema descriptions are tautological ('Declared type: string'), so real semantics for prompt, seed, aspect_ratio, callback_url, and timeout_ms are documented nowhere.

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 Imagen 4 task on RunAPI') and clarifies the modality ('text to image'). However, it does not differentiate itself from siblings like remix_image or get_task, which an agent could reasonably confuse it with when deciding what to call.

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 guidance on when to use this versus alternatives such as remix_image, nor on when to set wait=true versus polling via get_task. The agent must infer all routing decisions from the tool name alone.

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