imagen-4-mcp

remix_image

Generate an Imagen 4 image variation from source image URLs on RunAPI. Returns a task ID, status, and output URLs.

Instructions

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

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": {
      "source_image_urls": "<source_image_urls>"
    },
    "name": "remix_image"
  }
}

Input 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", "2:3", "3:2", "3:4", "4:3", "4:5", "5:4", "9:16", "16:9", "21:9", "auto".
`callback_url`	No	Declared type: string.
`output_format`	No	Declared type: string. Known values: "png", "jpg".
`poll_interval_ms`	No
`output_resolution`	No	Declared type: string. Known values: "1k", "2k", "4k".
`source_image_urls`	Yes	Declared type: array.

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 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\", \"2:3\", \"3:2\", \"3:4\", \"4:3\", \"4:5\", \"5:4\", \"9:16\", \"16:9\", \"21:9\", \"auto\"."
```
- removedInput schema / properties / aspect_ratio / enum
```
Removed value: -[
-  "1:1",
-  "2:3",
-  "3:2",
-  "3:4",
-  "4:3",
-  "4:5",
-  "5:4",
-  "9:16",
-  "16:9",
-  "21:9",
-  "auto"
-]
```
- addedInput schema / properties / callback_url / description
```
Added value: +"Declared type: string."
```
- removedInput schema / properties / model / enum
```
Removed value: -[
-  "imagen-4-pro-remix-image"
-]
```
- addedInput schema / properties / output_format / description
```
Added value: +"Declared type: string. Known values: \"png\", \"jpg\"."
```
- removedInput schema / properties / output_format / enum
```
Removed value: -[
-  "png",
-  "jpg"
-]
```
- addedInput schema / properties / output_resolution / description
```
Added value: +"Declared type: string. Known values: \"1k\", \"2k\", \"4k\"."
```
- 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 / description
```
Added value: +"Declared type: string."
```
- addedInput schema / properties / source_image_urls / description
```
Added value: +"Declared type: array."
```
- removedInput schema / properties / source_image_urls / maxItems
```
Removed value: -8
```
- removedInput schema / properties / source_image_urls / minItems
```
Removed value: -1
```
- addedInput schema / properties / timeout_ms / maximum
```
Added value: +9007199254740991
```
Changed2 schema fields changedv0.1.9Aug 5, 2026
- addedInput schema / properties / source_image_urls / maxItems
```
Added value: +8
```
- addedInput schema / properties / source_image_urls / minItems
```
Added value: +1
```
Changed5 schema fields changedv0.1.7Jul 13, 2026
- addedInput schema / properties / callback_url
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / prompt
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / source_image_urls / items
```
Added value: +{}
```
- addedInput schema / properties / source_image_urls / type
```
Added value: +"array"
```
- 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?

With no annotations, the description carries the full burden. It discloses only the return shape (task id, status, output URLs); it says nothing about asynchronous task submission, whether `wait: true` blocks, cost/pricing implications, rate limits, or model/credential prerequisites despite being a task-creating write operation.

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 tightly packed sentences with no filler and the operation stated up front. The grammar is slightly rough ('a Imagen 4 task'), but nothing is wasted.

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 task-creation tool with no annotations and no output schema, the description is far too thin: it omits async/polling behavior, the meaning of the required source images, and any tie-in to get_task for retrieving results. An agent cannot confidently invoke it from this text alone.

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 80%, so the schema already documents most fields (wait, model, aspect_ratio enum values, output_format, output_resolution). The description adds no parameter-level meaning, leaving the required `source_image_urls` (documented only as 'Declared type: array') and prompt/timeout semantics unclarified. Baseline 3 applies.

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?

The description names a specific verb ('Create') and resource ('Imagen 4 task on RunAPI') and parenthetically signals the remix/image-to-image nature. It distinguishes itself reasonably from text_to_image by the 'remix image' qualifier, though it never states explicitly that it transforms supplied source images rather than generating from text alone.

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, no exclusions, and no reference to the obvious sibling text_to_image or get_task for polling. The agent must infer that this is the image-to-image path purely from the tool name and the parenthetical.

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

Deploy Server