wan-mcp

edit_video

Submit a Wan RunAPI video modification task from a source video URL; returns task id, status, and output URLs for polling.

Instructions

Create a Wan task on RunAPI (edit video). 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.
`audio`	No	Declared type: boolean.
`model`	No	RunAPI model slug for this model line.
`prompt`	No	Declared type: string.
`watermark`	No	Declared type: boolean.
`timeout_ms`	No
`multi_shots`	No	Controls whether the generated video uses multiple shots with transitions instead of one continuous shot. Declared type: boolean.
`aspect_ratio`	No	Declared type: string.
`callback_url`	No	Declared type: string.
`audio_setting`	No	Declared type: string.
`negative_prompt`	No	Declared type: string.
`duration_seconds`	No	Declared type: integer.
`poll_interval_ms`	No
`source_video_url`	No	Declared type: string.
`output_resolution`	No	Declared type: string.
`source_video_urls`	No	Declared type: array.
`reference_image_url`	No	Declared type: string.
`enable_safety_checker`	No	Declared type: boolean.
`enable_prompt_expansion`	No	Declared type: boolean.

Schema Changelog

Changes observed during successful MCP inspections.

Changed23 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."
```
- addedInput schema / properties / audio / description
```
Added value: +"Declared type: boolean."
```
- addedInput schema / properties / audio_setting / description
```
Added value: +"Declared type: string."
```
- addedInput schema / properties / callback_url / description
```
Added value: +"Declared type: string."
```
- addedInput schema / properties / duration_seconds / description
```
Added value: +"Declared type: integer."
```
- changedInput schema / properties / duration_seconds / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / enable_prompt_expansion / description
```
Added value: +"Declared type: boolean."
```
- addedInput schema / properties / enable_safety_checker / description
```
Added value: +"Declared type: boolean."
```
- removedInput schema / properties / model / enum
```
Removed value: -[
-  "wan-2.6-edit-video",
-  "wan-2.6-flash-edit-video",
-  "wan-2.7-edit-video"
-]
```
- addedInput schema / properties / multi_shots / description
```
Added value: +"Controls whether the generated video uses multiple shots with transitions instead of one continuous shot. Declared type: boolean."
```
- addedInput schema / properties / negative_prompt / description
```
Added value: +"Declared type: string."
```
- addedInput schema / properties / output_resolution / description
```
Added value: +"Declared type: string."
```
- 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_url / 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_video_url / description
```
Added value: +"Declared type: string."
```
- addedInput schema / properties / source_video_urls / description
```
Added value: +"Declared type: array."
```
- addedInput schema / properties / timeout_ms / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / watermark / description
```
Added value: +"Declared type: boolean."
```
- addedInput schema / required
```
Added value: +[]
```
Changed17 schema fields changedv0.1.9Jul 31, 2026
- removedInput schema / properties / aspect_ratio / enum
```
Removed value: -[
-  "16:9",
-  "9:16",
-  "1:1",
-  "4:3",
-  "3:4"
-]
```
- addedInput schema / properties / audio
```
Added value: +{
+  "type": "boolean"
+}
```
- addedInput schema / properties / audio_setting
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / callback_url
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / duration_seconds
```
Added value: +{
+  "type": "number"
+}
```
- addedInput schema / properties / enable_prompt_expansion
```
Added value: +{
+  "type": "boolean"
+}
```
- addedInput schema / properties / enable_safety_checker
```
Added value: +{
+  "type": "boolean"
+}
```
- addedInput schema / properties / multi_shots
```
Added value: +{
+  "type": "boolean"
+}
```
- addedInput schema / properties / negative_prompt
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / output_resolution / enum
```
Removed value: -[
-  "720p",
-  "1080p"
-]
```
- addedInput schema / properties / prompt / type
```
Added value: +"string"
```
- addedInput schema / properties / reference_image_url
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / seed
```
Added value: +{
+  "type": "number"
+}
```
- addedInput schema / properties / source_video_url / type
```
Added value: +"string"
```
- addedInput schema / properties / source_video_urls / items
```
Added value: +{}
```
- addedInput schema / properties / source_video_urls / type
```
Added value: +"array"
```
- addedInput schema / properties / watermark
```
Added value: +{
+  "type": "boolean"
+}
```
First observedv0.1.6Jul 13, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations are present, so the description carries the full burden. It does disclose the async task pattern and the returned fields (task id, status, output URLs), which is useful, but it says nothing about required inputs (source_video_url?), whether wait=true blocks, cost/pricing implications, or failure behavior. For a 20-parameter generation tool with zero annotation coverage, that is a substantial gap.

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 compact sentences with the operation stated first and the return contract second — no filler or repetition. It is appropriately sized, though the parenthetical "(edit video)" is doing less work than a real scope statement would.

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?

A 20-parameter, zero-required, no-annotation, no-output-schema tool needs more than two sentences. The description partially compensates for the missing output schema by naming the returned fields, but it leaves the agent unable to tell which of source_video_url / source_video_urls / reference_image_url are actually needed for an edit, nor how the wait/poll parameters interact.

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 90%, so the schema already documents nearly all 20 parameters, and the description adds no parameter-level meaning beyond that. Baseline 3 is appropriate when the schema does the heavy lifting; the description contributes nothing extra here.

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 gives a verb and resource ("Create a Wan task on RunAPI (edit video)") and names the return shape, but "edit video" is never qualified — it does not say whether it restyles an existing source video, concatenates clips, or performs some other transform. Siblings like text_to_video and image_to_video imply this line is for editing a source video, but the description never makes that distinction explicit.

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 at all. Nothing tells the agent how this differs from text_to_video, image_to_video, or animate, nor that get_task is the alternative for polling an existing task, even though this tool also exposes wait/poll_interval_ms.

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

Deploy Server

edit_video

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools