hailuo-mcp

text_to_video

Create Hailuo video generation tasks from text prompts via RunAPI, returning task IDs, status, and output URLs.

Instructions

Create a Hailuo task on RunAPI (text to video). 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_video"
  }
}

Input Schema

Name	Required	Description
`wait`	No	Poll until the task reaches a terminal status.
`model`	No	RunAPI model slug for this model line.
`prompt`	No	Declared type: string.
`timeout_ms`	No
`callback_url`	No	Declared type: string.
`duration_seconds`	No	Declared type: integer.
`poll_interval_ms`	No
`prompt_optimizer`	No	Declared type: boolean.
`enable_safety_checker`	No	Declared type: boolean.

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedv0.3.0Oct 5, 2026
- changedInput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```
- 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_safety_checker / description
```
Added value: +"Declared type: boolean."
```
- removedInput schema / properties / model / enum
```
Removed value: -[
-  "hailuo-02-text-to-video-pro",
-  "hailuo-02-text-to-video-standard"
-]
```
- addedInput schema / properties / poll_interval_ms / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / prompt / description
```
Added value: +"Declared type: string."
```
- addedInput schema / properties / prompt_optimizer / description
```
Added value: +"Declared type: boolean."
```
- addedInput schema / properties / timeout_ms / maximum
```
Added value: +9007199254740991
```
- addedInput schema / required
```
Added value: +[]
```
Changed5 schema fields changedv0.1.7Aug 5, 2026
- addedInput schema / properties / callback_url
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / duration_seconds / enum
```
Removed value: -[
-  6,
-  10
-]
```
- addedInput schema / properties / enable_safety_checker
```
Added value: +{
+  "type": "boolean"
+}
```
- addedInput schema / properties / prompt
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / prompt_optimizer
```
Added value: +{
+  "type": "boolean"
+}
```
First observedv0.1.0Jun 24, 2026

TDQS

B3.2/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 full burden. It usefully discloses that this is asynchronous task creation returning a task id and status, plus the schema's 'wait' default of polling to terminal status. However it omits auth requirements, rate limits, and what happens if wait is false (fire-and-forget vs. polling), leaving meaningful behavioral gaps.

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 core action front-loaded and no wasted words. It is appropriately sized, though it sacrifices some useful detail for brevity.

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

Completeness3/5

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

With 9 parameters and no output schema or annotations, the description is only partially sufficient. It helpfully names the return shape (task id, status, output URLs), but does not explain the wait/poll/callback interaction an agent needs to drive this async tool 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 description coverage is 78%, close to the high-coverage baseline, so the schema already documents most parameters. The description adds nothing about parameters (prompt content, duration, safety checker, callback), so baseline 3 is appropriate.

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) and resource (a Hailuo task on RunAPI) and disambiguates from the sibling image_to_video with '(text to video)'. It is clear what the tool produces, though the 'Hailuo/RunAPI' naming adds external context that isn't further explained.

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 explicit when-to-use or when-not-to-use guidance and no mention of alternatives. The sibling get_task clearly exists for polling results, yet the description never routes the agent there or explains the relationship between creating a task and retrieving it.

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

Deploy Server