@runapi.ai/happyhorse-mcp

Official

Overview Schema Source Related Servers Discussions Admin

edit_video

Edit videos by submitting a source video URL to create a HappyHorse task on RunAPI. Returns task ID, status, and output URLs.

Instructions

Create a HappyHorse 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.
`model`	No	RunAPI model slug for this model line.
`prompt`	No	Declared type: string.
`timeout_ms`	No
`callback_url`	No	Declared type: string.
`audio_setting`	No	Declared type: string. Known values: "auto", "original".
`poll_interval_ms`	No
`source_video_url`	Yes	Declared type: string.
`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.

Changed15 schema fields changedv0.2.0Oct 5, 2026
- changedInput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```
- addedInput schema / properties / audio_setting / description
```
Added value: +"Declared type: string. Known values: \"auto\", \"original\"."
```
- removedInput schema / properties / audio_setting / enum
```
Removed value: -[
-  "auto",
-  "original"
-]
```
- addedInput schema / properties / callback_url / description
```
Added value: +"Declared type: string."
```
- removedInput schema / properties / model / enum
```
Removed value: -[
-  "happyhorse-edit-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."
```
- removedInput schema / properties / reference_image_urls / maxItems
```
Removed value: -5
```
- 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 / timeout_ms / maximum
```
Added value: +9007199254740991
```
Changed8 schema fields changedv0.1.7Jul 22, 2026
- addedInput schema / properties / callback_url
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / prompt
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / reference_image_urls / items
```
Added value: +{}
```
- addedInput schema / properties / reference_image_urls / maxItems
```
Added value: +5
```
- addedInput schema / properties / reference_image_urls / type
```
Added value: +"array"
```
- addedInput schema / properties / seed
```
Added value: +{
+  "type": "number"
+}
```
- addedInput schema / properties / source_video_url / type
```
Added value: +"string"
```
- addedInput schema / required
```
Added value: +[
+  "source_video_url"
+]
```
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?

With no annotations provided, the description carries the full burden, and it does disclose useful behavioral context: this is an asynchronous task creation that returns a task id, status, and output URLs. However, it says nothing about authentication (a sibling 'login' tool implies auth is needed), cost, or what happens to the source video, which leaves meaningful gaps for a mutation endpoint.

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 action front-loaded and no filler; the parenthetical '(edit video)' is mildly redundant with the tool name but aids scannability. Nothing else is wasted.

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 an 11-parameter, single-required-argument async video tool with no annotations and no output schema, the description covers the return shape but omits key operational context: the required source_video_url, the synchronous vs. polling (wait/timeout_ms) behavior, and auth prerequisites. It is minimally adequate but not complete.

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%, well above the baseline threshold, so the schema already documents most parameters (wait=poll until terminal, audio_setting enum-known values, output_resolution values). The description adds no parameter semantics at all, so a 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?

The description states a specific verb+resource: it creates a HappyHorse task that edits video, and notes the RunAPI platform. It does not explicitly differentiate itself from siblings like image_to_video or text_to_video (e.g., by noting it takes an existing source video), so it falls short of a 5.

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 guidance, no exclusions, and no mention of alternatives such as image_to_video or text_to_video. The agent must infer from the tool name that this is the variant for editing an existing video rather than generating one from scratch.

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