WanMCP

wan_get_tasks_batch

Check the status of up to 50 video generation tasks in a single request, retrieving their current status and video information.

Instructions

Query multiple video generation tasks at once.

Efficiently check the status of multiple tasks in a single request.

Returns:
    Status and video information for all queried tasks.

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": {
      "task_ids": "<task_ids>"
    },
    "name": "wan_get_tasks_batch"
  }
}

Input Schema

Name	Required	Description	Default
`task_ids`	Yes	List of task IDs to query. Maximum recommended batch size is 50 tasks.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Apr 25, 2026

TDQS

A4.1/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It states the return includes status and video information, which is basic. It does not disclose rate limits, authentication needs, or any side effects. The mention of max batch size is in the schema description, not the main description.

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?

The description is three sentences: purpose, benefit, and return. It is front-loaded and concise, with no unnecessary information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one parameter, output schema exists), the description sufficiently covers what the tool does and returns. The output schema handles return value details, so no further elaboration is needed.

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 100% for the single parameter 'task_ids', with a clear description of its purpose and constraints. The main description adds no additional semantic value beyond what the schema already provides, meeting the baseline for high coverage.

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

Purpose5/5

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

The description uses the specific verb 'query' and resource 'multiple video generation tasks', clearly distinguishing it from the sibling tool 'wan_get_task' which queries a single task. The phrase 'at once' and 'batch' reinforce the batching behavior.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for checking multiple tasks efficiently, and the sibling tool names provide clear contrast with 'wan_get_task' for single tasks. However, it does not explicitly state when not to use or mention alternative scenarios.

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

Deploy Server