Ideogram V3 MCP Server

edit_image

Edit images with Ideogram V3 by submitting a source image and mask to RunAPI, then get task IDs, status, and output URLs.

Instructions

Create a Ideogram V3 task on RunAPI (edit 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.
`style`	No	Declared type: string.
`prompt`	No	Declared type: string.
`mask_url`	Yes	Declared type: string.
`timeout_ms`	No
`callback_url`	No	Declared type: string.
`output_count`	No	Declared type: integer. Known values: 1, 2, 3, 4.
`rendering_speed`	No	Declared type: string. Known values: "turbo", "balanced", "quality".
`poll_interval_ms`	No
`source_image_url`	Yes	Declared type: string.
`reference_image_urls`	No	Declared type: array.
`enable_prompt_expansion`	No	Declared type: boolean.

Schema Changelog

Changes observed during successful MCP inspections.

Changed18 schema fields changedv0.2.0Oct 5, 2026
- changedInput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```
- addedInput schema / properties / callback_url / description
```
Added value: +"Declared type: string."
```
- addedInput schema / properties / enable_prompt_expansion / description
```
Added value: +"Declared type: boolean."
```
- addedInput schema / properties / mask_url / description
```
Added value: +"Declared type: string."
```
- removedInput schema / properties / model / enum
```
Removed value: -[
-  "ideogram-v3-character-edit",
-  "ideogram-v3-edit"
-]
```
- 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 / 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 / style / description
```
Added value: +"Declared type: string."
```
- addedInput schema / properties / timeout_ms / maximum
```
Added value: +9007199254740991
```
Changed9 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 / mask_url
```
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 / seed
```
Added value: +{
+  "type": "number"
+}
```
- addedInput schema / properties / source_image_url / type
```
Added value: +"string"
```
- removedInput schema / properties / style / enum
```
Removed value: -[
-  "auto",
-  "realistic",
-  "fiction"
-]
```
- addedInput schema / required
```
Added value: +[
+  "source_image_url",
+  "mask_url"
+]
```
First observedv0.1.0Jun 24, 2026

TDQS

B3.2/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 behavioral burden. It does add genuinely useful context by disclosing that this is an asynchronous task-creation model returning a task id and status (implying get_task follow-up), which is not derivable from the schema. However, it omits permissions, whether an edit is destructive to the source, rate limits, and how the mask constrains the operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with zero filler, and the core action is front-loaded before the return-value clause. Every clause earns its place.

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?

This is a 14-parameter tool with no output schema and no annotations, so the description should be doing far more work. It never explains the mask/source-image contract, the meaning of wait/poll_interval_ms, or the model/style options, leaving an agent under-informed for a fairly complex invocation.

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 86% across 14 parameters, so the schema largely documents itself and the baseline is 3. The description adds no parameter-level meaning (no explanation of mask_url, source_image_url, prompt, style, or wait semantics) beyond what the schema already states.

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?

Names a specific verb and resource ('Create a Ideogram V3 task on RunAPI (edit image)') and states the return contract (task id, status, output URLs), so an agent knows this kicks off an image-editing job. It does not explicitly differentiate itself from the semantically nearby siblings remix_image and reframe_image, which keeps it short of a 5.

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 statement of when to choose this tool over remix_image, reframe_image, or text_to_image, and no prerequisites (e.g. that a source image and mask are mandatory) are called out. The parenthetical '(edit image)' implies the domain but gives no routing guidance.

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