Skip to main content
Glama
runapi-ai

@runapi.ai/happyhorse-mcp

Official
by runapi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

image_to_video

Create a HappyHorse task on RunAPI to generate a video from a first-frame image URL, returning a task ID, status, and output URLs.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seedNoDeclared type: integer.
waitNoPoll until the task reaches a terminal status.
modelNoRunAPI model slug for this model line.
promptNoDeclared type: string.
timeout_msNo
callback_urlNoDeclared type: string.
duration_secondsNoDeclared type: integer.
poll_interval_msNo
output_resolutionNoDeclared type: string. Known values: "720p", "1080p".
first_frame_image_urlYesDeclared type: string.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv0.2.0
    • 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 / first_frame_image_url / description
      Added value: +"Declared type: string."
    • removedInput schema / properties / model / enum
      Removed value: -[
-  "happyhorse-1.0-i2v",
-  "happyhorse-image-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 / 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
  2. Addedv0.1.8
  3. Removedv0.1.7
  4. First observedv0.1.0

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 disclosure burden. It reveals that a task is created and what comes back (task id, status, output URLs), which is useful, but says nothing about async/polling behavior despite a 'wait' parameter defaulting to true, nor about auth, cost, rate limits, or failure modes.

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 action front-loaded and the return contract immediately after; no filler. It is efficient, though it spends its second sentence on return values while leaving usage and behavioral context unaddressed.

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 10 parameters, no annotations, and no output schema, the description does its duty of describing the return shape, which is genuinely helpful. However, for an async task-creation tool it omits polling/termination semantics and model selection context that an agent needs to invoke it confidently.

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 coverage is 80%, so the baseline is 3. The description adds no parameter-level meaning at all — nothing about seed, model slug choice, duration_seconds, output_resolution, or how wait/timeout_ms/poll_interval_ms interact.

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 HappyHorse task on RunAPI) and names the modality ('image to video'), which implicitly separates it from text_to_video and edit_video. It stops short of explicitly naming those siblings or stating what artifact it operates on, so it lands below the 5 bar.

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 or when-not-to-use guidance, no mention of prerequisites (e.g. an existing image URL), and no routing to the sibling tools (text_to_video, edit_video, get_task) that a caller could easily confuse this with. The modality label only vaguely implies usage.

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

Deploy Server

Other Tools