hailuo-mcp

image_to_video

Convert a source image into a video using Hailuo. Submit the first-frame image URL to create a RunAPI task, optionally wait, and get task status and output video URLs.

Instructions

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

Input Schema

TableJSON 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.
`output_resolution`	No	Declared type: string.
`last_frame_image_url`	No	Declared type: string.
`enable_safety_checker`	No	Enable the safety checker. Declared type: boolean.
`first_frame_image_url`	Yes	Declared type: string.

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 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: +"Enable the safety checker. Declared type: boolean."
```
- addedInput schema / properties / first_frame_image_url / description
```
Added value: +"Declared type: string."
```
- addedInput schema / properties / last_frame_image_url / description
```
Added value: +"Declared type: string."
```
- removedInput schema / properties / model / enum
```
Removed value: -[
-  "hailuo-02-image-to-video-pro",
-  "hailuo-02-image-to-video-standard",
-  "hailuo-2.3-image-to-video-pro",
-  "hailuo-2.3-image-to-video-standard"
-]
```
- 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 / prompt_optimizer / description
```
Added value: +"Declared type: boolean."
```
- addedInput schema / properties / timeout_ms / maximum
```
Added value: +9007199254740991
```
Changed9 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 / first_frame_image_url / type
```
Added value: +"string"
```
- addedInput schema / properties / last_frame_image_url / type
```
Added value: +"string"
```
- removedInput schema / properties / output_resolution / enum
```
Removed value: -[
-  "512p",
-  "768p",
-  "1080p"
-]
```
- addedInput schema / properties / prompt
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / prompt_optimizer
```
Added value: +{
+  "type": "boolean"
+}
```
- addedInput schema / required
```
Added value: +[
+  "first_frame_image_url"
+]
```
First observedv0.1.0Jun 24, 2026

TDQS

B3.4/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 that this is an asynchronous task-creation endpoint returning a task id and status, which is genuinely useful. However, it omits the blocking behavior implied by the wait parameter default, timeout semantics, cost implications, and the fact that the returned URLs may not be immediately available.

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, front-loaded with the action and platform, with the return shape in the second sentence. Nothing is wasted, though the parenthetical is slightly redundant with the tool name.

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?

For a 12-parameter, no-annotation, no-output-schema tool, the description usefully covers the return values, which compensates for the missing output schema. But it leaves key generation controls (duration, resolution, prompt, last-frame image) and the polling/timeout behavior entirely to the schema.

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 83%, above the 80% threshold, so the schema already documents nearly all parameters. The description adds no per-parameter meaning (model slug, duration_seconds, output_resolution, prompt are unexplained), so baseline 3 applies.

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), the resource (a Hailuo task on RunAPI), and the modality (image to video), which separates it from the sibling text_to_video. It stops short of naming that sibling explicitly, so it is clear but not fully differentiated.

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

Usage Guidelines3/5

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

The parenthetical '(image to video)' implies the usage context and the existence of the text_to_video alternative, but the description never states when to pick this tool over that one, nor any prerequisites such as image URL accessibility or account/auth needs.

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

Deploy Server

image_to_video

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools