Ideogram V3 MCP Server

remix_image

Remix an existing image using Ideogram V3 on RunAPI by providing a source image URL. Returns a task ID, status, and generated output URLs.

Instructions

Create a Ideogram V3 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_url": "<source_image_url>"
    },
    "name": "remix_image"
  }
}

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.
`style`	No	Declared type: string. Known values: "auto", "realistic", "fiction", "general", "design".
`prompt`	No	Declared type: string.
`strength`	No	Declared type: number.
`timeout_ms`	No
`aspect_ratio`	No	Declared type: string. Known values: "1:1", "3:4", "9:16", "4:3", "16:9".
`callback_url`	No	Declared type: string.
`output_count`	No	Declared type: integer. Known values: 1, 2, 3, 4.
`negative_prompt`	No	Declared type: string.
`rendering_speed`	No	Declared type: string. Known values: "turbo", "balanced", "quality".
`poll_interval_ms`	No
`source_image_url`	Yes	Declared type: string.
`reference_mask_urls`	No	Declared type: array.
`reference_image_urls`	No	Declared type: array.
`enable_prompt_expansion`	No	Declared type: boolean.
`style_reference_image_urls`	No	Declared type: array.

Schema Changelog

Changes observed during successful MCP inspections.

Changed24 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\", \"3:4\", \"9:16\", \"4:3\", \"16:9\"."
```
- removedInput schema / properties / aspect_ratio / enum
```
Removed value: -[
-  "1:1",
-  "3:4",
-  "9:16",
-  "4:3",
-  "16:9"
-]
```
- addedInput schema / properties / callback_url / description
```
Added value: +"Declared type: string."
```
- addedInput schema / properties / enable_prompt_expansion / description
```
Added value: +"Declared type: boolean."
```
- removedInput schema / properties / model / enum
```
Removed value: -[
-  "ideogram-v3-character-remix",
-  "ideogram-v3-remix"
-]
```
- addedInput schema / properties / negative_prompt / description
```
Added value: +"Declared type: string."
```
- addedInput schema / properties / output_count / description
```
Added value: +"Declared type: integer. Known values: 1, 2, 3, 4."
```
- removedInput schema / properties / output_count / enum
```
Removed value: -[
-  1,
-  2,
-  3,
-  4
-]
```
- changedInput schema / properties / output_count / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / poll_interval_ms / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / prompt / description
```
Added value: +"Declared type: string."
```
- addedInput schema / properties / reference_image_urls / description
```
Added value: +"Declared type: array."
```
- addedInput schema / properties / reference_mask_urls / description
```
Added value: +"Declared type: array."
```
- addedInput schema / properties / rendering_speed / description
```
Added value: +"Declared type: string. Known values: \"turbo\", \"balanced\", \"quality\"."
```
- removedInput schema / properties / rendering_speed / enum
```
Removed value: -[
-  "turbo",
-  "balanced",
-  "quality"
-]
```
- addedInput schema / properties / seed / description
```
Added value: +"Declared type: integer."
```
- changedInput schema / properties / seed / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / source_image_url / description
```
Added value: +"Declared type: string."
```
- addedInput schema / properties / strength / description
```
Added value: +"Declared type: number."
```
- addedInput schema / properties / style / description
```
Added value: +"Declared type: string. Known values: \"auto\", \"realistic\", \"fiction\", \"general\", \"design\"."
```
- removedInput schema / properties / style / enum
```
Removed value: -[
-  "auto",
-  "realistic",
-  "fiction",
-  "general",
-  "design"
-]
```
- addedInput schema / properties / style_reference_image_urls / description
```
Added value: +"Declared type: array."
```
- addedInput schema / properties / timeout_ms / maximum
```
Added value: +9007199254740991
```
Changed12 schema fields changedv0.1.7Aug 5, 2026
- addedInput schema / properties / callback_url
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / enable_prompt_expansion
```
Added value: +{
+  "type": "boolean"
+}
```
- addedInput schema / properties / negative_prompt
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / prompt
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / reference_image_urls
```
Added value: +{
+  "items": {},
+  "type": "array"
+}
```
- addedInput schema / properties / reference_mask_urls
```
Added value: +{
+  "items": {},
+  "type": "array"
+}
```
- addedInput schema / properties / seed
```
Added value: +{
+  "type": "number"
+}
```
- addedInput schema / properties / source_image_url / type
```
Added value: +"string"
```
- addedInput schema / properties / strength
```
Added value: +{
+  "type": "number"
+}
```
- addedInput schema / properties / style_reference_image_urls / items
```
Added value: +{}
```
- addedInput schema / properties / style_reference_image_urls / type
```
Added value: +"array"
```
- addedInput schema / required
```
Added value: +[
+  "source_image_url"
+]
```
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 behavioral burden. It discloses only the return shape (task id, status, output URLs); it does not explain that the call is asynchronous, how the 'wait'/'poll_interval_ms' polling behaves, what auth is required, or what happens with callback_url.

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 the operation stated first and the return values second; no filler. Slightly dense but front-loaded and efficient.

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

Completeness3/5

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

For an 18-parameter asynchronous task tool with no annotations and no output schema, the description usefully states the return values but omits the async/polling model and any usage context. It covers the minimal essentials while leaving notable behavioral gaps for such a complex tool.

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 89%, so the schema already documents nearly all 18 parameters, which sets the baseline at 3. The description adds no parameter-level meaning beyond implying a source image is needed for the remix.

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) plus resource (Ideogram V3 task, remix image) and clarifies it acts on a source image, which hints at the distinction from text_to_image. However, it does not explain how 'remix' differs from sibling edit_image or reframe_image, so an agent cannot fully route between the image-manipulation siblings from the description 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 or when-not-to-use guidance and no mention of the alternative image tools (edit_image, reframe_image, text_to_image). The agent is left to infer from the name which operation applies.

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

Deploy Server