@runapi.ai/happyhorse-mcp

Official

Overview Schema Source Related Servers Discussions Admin

text_to_video

Generate a video from a text prompt via RunAPI. Returns a task id, status, and output URLs, with optional polling until the task completes.

Instructions

Create a HappyHorse task on RunAPI (text to 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.
`model`	No	RunAPI model slug for this model line.
`prompt`	No	Declared type: string.
`timeout_ms`	No
`aspect_ratio`	No	Declared type: string. Known values: "16:9", "9:16", "1:1", "4:3", "3:4".
`callback_url`	No	Declared type: string.
`duration_seconds`	No	Declared type: integer.
`poll_interval_ms`	No
`output_resolution`	No	Declared type: string. Known values: "720p", "1080p".
`reference_image_urls`	No	Declared type: array.

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedv0.2.0Oct 5, 2026
- changedInput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```
- addedInput schema / properties / aspect_ratio / description
```
Added value: +"Declared type: string. Known values: \"16:9\", \"9:16\", \"1:1\", \"4:3\", \"3:4\"."
```
- removedInput schema / properties / aspect_ratio / enum
```
Removed value: -[
-  "16:9",
-  "9:16",
-  "1:1",
-  "4:3",
-  "3:4"
-]
```
- 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"
```
- removedInput schema / properties / model / enum
```
Removed value: -[
-  "happyhorse-1.0-r2v",
-  "happyhorse-1.0-t2v",
-  "happyhorse-character",
-  "happyhorse-text-to-video"
-]
```
- addedInput schema / properties / output_resolution / description
```
Added value: +"Declared type: string. Known values: \"720p\", \"1080p\"."
```
- removedInput schema / properties / output_resolution / enum
```
Removed value: -[
-  "720p",
-  "1080p"
-]
```
- 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_urls / description
```
Added value: +"Declared type: array."
```
- addedInput schema / properties / seed / description
```
Added value: +"Declared type: integer."
```
- changedInput schema / properties / seed / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / timeout_ms / maximum
```
Added value: +9007199254740991
```
- addedInput schema / required
```
Added value: +[]
```

Changed1 schema field changedv0.1.8Aug 5, 2026

changedInput schema / properties / model / enum

Previous value: -[
-  "happyhorse-character",
-  "happyhorse-text-to-video"
-]New value: +[
+  "happyhorse-1.0-r2v",
+  "happyhorse-1.0-t2v",
+  "happyhorse-character",
+  "happyhorse-text-to-video"
+]

Changed6 schema fields changedv0.1.7Jul 22, 2026
- addedInput schema / properties / callback_url
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / duration_seconds
```
Added value: +{
+  "type": "number"
+}
```
- addedInput schema / properties / prompt
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / reference_image_urls / items
```
Added value: +{}
```
- addedInput schema / properties / reference_image_urls / type
```
Added value: +"array"
```
- addedInput schema / properties / seed
```
Added value: +{
+  "type": "number"
+}
```
First observedv0.1.0Jun 24, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden, and it discloses very little: it omits that this is an asynchronous task creation, that cost may be incurred, whether auth is required, and how the 'wait' default (true) changes behavior. It adds only the shape of the return (task id, status, output URLs), which is the one genuinely useful behavioral hint.

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 purpose front-loaded and the return contract second. Nothing is padded, though it is thin rather than efficient-with-substance.

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 11 parameters, zero required, no annotations, and no output schema, the description is only marginally sufficient. It does cover the return shape (task id, status, output URLs), which partially compensates for the missing output schema, but the async/cost/auth behavior of a task-creation tool is left entirely unstated.

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 82%, so the schema already documents most parameters (including enum-like known values for aspect_ratio and output_resolution). The description adds no parameter-level meaning, which is acceptable at this coverage level but earns no uplift.

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 concrete verb and resource ('Create a HappyHorse task on RunAPI') and the modality qualifier '(text to video)' distinguishes it from image_to_video and edit_video. It stops short of explicitly naming or contrasting those siblings, but the resource+modality pairing is unambiguous.

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 guidance on when to choose this over image_to_video or edit_video, and no mention of prerequisites such as authentication or pricing checks despite check_pricing and login being siblings. The agent must infer selection purely from the modality parenthetical.

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

Deploy Server

text_to_video

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools