wan-mcp

animate

Create a Wan RunAPI task from a source image and reference video to generate motion video; returns task ID, status, and output URLs.

Instructions

Create a Wan task on RunAPI (animate). 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>",
      "reference_video_url": "<reference_video_url>"
    },
    "name": "animate"
  }
}

Input Schema

Name	Required	Description
`wait`	No	Poll until the task reaches a terminal status.
`model`	No	RunAPI model slug for this model line.
`timeout_ms`	No
`callback_url`	No	Declared type: string.
`poll_interval_ms`	No
`source_image_url`	Yes	Declared type: string.
`output_resolution`	No	Declared type: string. Known values: "480p", "580p", "720p".
`reference_video_url`	Yes	Declared type: string.
`enable_safety_checker`	No	Declared type: boolean.

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv0.2.0Oct 7, 2026
- changedInput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```
- addedInput schema / properties / callback_url / description
```
Added value: +"Declared type: string."
```
- addedInput schema / properties / enable_safety_checker / description
```
Added value: +"Declared type: boolean."
```
- removedInput schema / properties / model / enum
```
Removed value: -[
-  "wan-2.2-animate-move",
-  "wan-2.2-animate-replace"
-]
```
- addedInput schema / properties / output_resolution / description
```
Added value: +"Declared type: string. Known values: \"480p\", \"580p\", \"720p\"."
```
- removedInput schema / properties / output_resolution / enum
```
Removed value: -[
-  "480p",
-  "580p",
-  "720p"
-]
```
- addedInput schema / properties / poll_interval_ms / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / reference_video_url / description
```
Added value: +"Declared type: string."
```
- addedInput schema / properties / source_image_url / description
```
Added value: +"Declared type: string."
```
- addedInput schema / properties / timeout_ms / maximum
```
Added value: +9007199254740991
```
Changed5 schema fields changedv0.1.9Jul 31, 2026
- addedInput schema / properties / callback_url
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / enable_safety_checker
```
Added value: +{
+  "type": "boolean"
+}
```
- addedInput schema / properties / reference_video_url / type
```
Added value: +"string"
```
- addedInput schema / properties / source_image_url / type
```
Added value: +"string"
```
- addedInput schema / required
```
Added value: +[
+  "source_image_url",
+  "reference_video_url"
+]
```
First observedv0.1.6Jul 13, 2026

TDQS

C2.8/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 burden, and it does disclose the async task pattern and return shape (task id, status, output URLs). However it never mentions the long-running/polling nature implied by the 'wait' and 'poll_interval_ms' parameters, nor cost, auth, or rate limits.

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, front-loaded with the action and followed by the return shape; nothing is padded. It loses a point only because the terse phrasing leans on unexplained provider jargon rather than spending a few words on what the tool produces.

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 9-parameter generative media tool with no annotations and no output schema, the description is far too thin. It explains the return fields but not the async lifecycle, the roles of the image/video inputs, or how polling/timeout interact, leaving an agent under-equipped to call it correctly.

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 coverage is 78%, just under the high-coverage threshold, and several parameters (source_image_url, reference_video_url, callback_url, enable_safety_checker) carry only 'Declared type' placeholders. The description adds no parameter meaning beyond the schema, so a baseline-adjacent 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

It states a verb and resource ('Create a Wan task on RunAPI (animate)'), so the general action is clear. But it does not differentiate from the close siblings image_to_video and text_to_video, and 'animate' plus 'Wan task' is provider jargon rather than a description of what the animation actually does with a source image and reference video.

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 and no mention of alternatives, despite four visually similar siblings (image_to_video, text_to_video, edit_video, speech_to_video). An agent cannot infer from the text alone why it should pick 'animate' over image_to_video.

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

Deploy Server