Ideogram V3 MCP Server

text_to_image

Generate images from written prompts via Ideogram V3 on RunAPI, returning task IDs, status, and output URLs.

Instructions

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "text_to_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.
`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
`reference_image_urls`	No	Declared type: array.
`enable_prompt_expansion`	No	Declared type: boolean.

Schema Changelog

Changes observed during successful MCP inspections.

Changed21 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",
-  "ideogram-v3-text-to-image"
-]

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 / 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 / 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 / timeout_ms / maximum
```
Added value: +9007199254740991
```
addedInput schema / required
```
Added value: +[]
```

Changed6 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 / seed
```
Added value: +{
+  "type": "number"
+}
```
First observedv0.1.0Jun 24, 2026

TDQS

B3.1/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 load. It does add real value by disclosing the async task model and the return shape (task id, status, output URLs), which no output schema supplies. However, it omits auth needs, cost/pricing implications, and how the wait/poll parameters interact with the returned task id.

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 action front-loaded and the return contract second. No filler, though the phrasing 'Create a Ideogram V3 task on RunAPI' is slightly awkward and the parenthetical repeats the tool name.

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 14-parameter generation tool with no annotations and no output schema, the description is thin. It covers the return contract but says nothing about required inputs despite prompt obviously being essential, cost checks, polling via get_task, or how the wait/timeout_ms/callback_url options change behavior.

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%, so the schema already documents most of the 14 parameters, including enum-like known values for style, aspect_ratio, and rendering_speed. The description adds no parameter detail (e.g., model slug, output_count, callback_url) beyond that baseline.

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 (Create) plus the resource (Ideogram V3 task via RunAPI) and disambiguates with the parenthetical '(text to image)'. That distinguishes it from image-editing siblings (edit_image, reframe_image, remix_image), though it never names them directly.

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 prerequisites, and no named alternative. The '(text to image)' tag hints at the domain but does not tell the agent when to pick this over remix_image or edit_image, nor that get_task/check_pricing may be needed alongside it.

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

Deploy Server