wan-mcp

text_to_image

Generate images from text prompts via RunAPI, returning a task ID, status, and output URLs.

Instructions

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

Input Schema

TableJSON 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.
`bbox_list`	No	Declared type: array.
`watermark`	No	Declared type: boolean.
`timeout_ms`	No
`aspect_ratio`	No	Declared type: string. Known values: "1:1", "16:9", "4:3", "21:9", "3:4", "9:16", "8:1", "1:8".
`callback_url`	No	Declared type: string.
`output_count`	No	Declared type: integer.
`color_palette`	No	Declared type: array.
`thinking_mode`	No	Declared type: boolean.
`poll_interval_ms`	No
`enable_sequential`	No	Declared type: boolean.
`output_resolution`	No	Declared type: string. Known values: "1k", "2k", "4k".
`source_image_urls`	No	Declared type: array.
`enable_safety_checker`	No	Declared type: boolean.

Schema Changelog

Changes observed during successful MCP inspections.

Changed22 schema fields changedv0.2.0Oct 7, 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\", \"4:3\", \"21:9\", \"3:4\", \"9:16\", \"8:1\", \"1:8\"."
```
- removedInput schema / properties / aspect_ratio / enum
```
Removed value: -[
-  "1:1",
-  "16:9",
-  "4:3",
-  "21:9",
-  "3:4",
-  "9:16",
-  "8:1",
-  "1:8"
-]
```
- addedInput schema / properties / bbox_list / description
```
Added value: +"Declared type: array."
```
- addedInput schema / properties / callback_url / description
```
Added value: +"Declared type: string."
```
- addedInput schema / properties / color_palette / description
```
Added value: +"Declared type: array."
```
- addedInput schema / properties / enable_safety_checker / description
```
Added value: +"Declared type: boolean."
```
- addedInput schema / properties / enable_sequential / description
```
Added value: +"Declared type: boolean."
```
- removedInput schema / properties / model / enum
```
Removed value: -[
-  "wan-2.7-image",
-  "wan-2.7-image-pro"
-]
```
- addedInput schema / properties / output_count / description
```
Added value: +"Declared type: integer."
```
- changedInput schema / properties / output_count / type
```
Previous value: -"number"New value: +"integer"
```
- 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 / seed / description
```
Added value: +"Declared type: integer."
```
- changedInput schema / properties / seed / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / source_image_urls / description
```
Added value: +"Declared type: array."
```
- addedInput schema / properties / thinking_mode / description
```
Added value: +"Declared type: boolean."
```
- addedInput schema / properties / timeout_ms / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / watermark / description
```
Added value: +"Declared type: boolean."
```
- addedInput schema / required
```
Added value: +[]
```
Changed11 schema fields changedv0.1.9Jul 31, 2026
- addedInput schema / properties / bbox_list
```
Added value: +{
+  "items": {},
+  "type": "array"
+}
```
- addedInput schema / properties / callback_url
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / color_palette
```
Added value: +{
+  "items": {},
+  "type": "array"
+}
```
- addedInput schema / properties / enable_safety_checker
```
Added value: +{
+  "type": "boolean"
+}
```
- addedInput schema / properties / enable_sequential
```
Added value: +{
+  "type": "boolean"
+}
```
- addedInput schema / properties / output_count
```
Added value: +{
+  "type": "number"
+}
```
- addedInput schema / properties / prompt
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / seed
```
Added value: +{
+  "type": "number"
+}
```
- addedInput schema / properties / source_image_urls
```
Added value: +{
+  "items": {},
+  "type": "array"
+}
```
- addedInput schema / properties / thinking_mode
```
Added value: +{
+  "type": "boolean"
+}
```
- addedInput schema / properties / watermark
```
Added value: +{
+  "type": "boolean"
+}
```
First observedv0.1.6Jul 13, 2026

TDQS

B3.1/5.0

Behavior3/5

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

No annotations exist, so the description carries the burden. It does disclose the return shape (task id, status, output URLs), which is valuable with no output schema, and implies an async task model. However, it never explains the polling behavior implied by 'wait', 'timeout_ms', and 'poll_interval_ms', nor cost, auth, or rate-limit considerations.

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 no filler and the action front-loaded. The jargon ('Wan task on RunAPI') is slightly opaque but does not waste words.

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 17-parameter generative tool with zero annotations and no output schema, this is thin. Return values are mentioned, which helps, but there is nothing about async/wait semantics, valid model slugs, cost (despite a check_pricing sibling), or how to poll with get_task.

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 88%, so the schema already documents the parameters, and the description adds no parameter-level meaning. Baseline 3 is appropriate when the schema does the heavy lifting.

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 clear verb and resource: creating a text-to-image Wang task via RunAPI, and the parenthetical '(text to image)' distinguishes it from the sibling text_to_video. It stops short of naming alternatives explicitly, but the purpose is unambiguous.

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?

No when-to-use guidance, no exclusions, and no mention of the sibling tools an agent must choose between (text_to_video, edit_video, animate). Nothing tells the agent which model line or scenario this tool is appropriate for.

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