@runapi.ai/runway-aleph-mcp

Official

by runapi-ai

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

edit_video

Create a Runway Aleph task on RunAPI to edit a source video using a prompt; returns task ID, status, and output URLs.

Instructions

Create a Runway Aleph 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`	Yes	Declared type: string.
`watermark`	No	Declared type: string.
`timeout_ms`	No
`aspect_ratio`	No	Declared type: string. Known values: "16:9", "9:16", "4:3", "3:4", "1:1", "21:9".
`callback_url`	No	Declared type: string.
`poll_interval_ms`	No
`source_video_url`	Yes	Declared type: string.
`reference_image_url`	No	Declared type: string.

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 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\", \"4:3\", \"3:4\", \"1:1\", \"21:9\"."
```
- removedInput schema / properties / aspect_ratio / enum
```
Removed value: -[
-  "16:9",
-  "9:16",
-  "4:3",
-  "3:4",
-  "1:1",
-  "21:9"
-]
```
- addedInput schema / properties / callback_url / description
```
Added value: +"Declared type: string."
```
- removedInput schema / properties / model / enum
```
Removed value: -[
-  "runway-aleph"
-]
```
- 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_url / 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 / source_video_url / description
```
Added value: +"Declared type: string."
```
- addedInput schema / properties / timeout_ms / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / watermark / description
```
Added value: +"Declared type: string."
```
Changed7 schema fields changedv0.1.7Aug 5, 2026
- addedInput schema / properties / callback_url
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / prompt / type
```
Added value: +"string"
```
- addedInput schema / properties / reference_image_url
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / seed
```
Added value: +{
+  "type": "number"
+}
```
- addedInput schema / properties / source_video_url / type
```
Added value: +"string"
```
- addedInput schema / properties / watermark
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / required
```
Added value: +[
+  "prompt",
+  "source_video_url"
+]
```
First observedv0.1.0Jun 24, 2026

TDQS

B3.3/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. It does disclose that the call is asynchronous ('task') and what comes back ('task id, status, and output URLs'), which is genuinely useful. It omits auth requirements, cost/rate considerations, and whether the operation is reversible in any sense.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the action and the return shape. The parenthetical '(edit video)' is mildly redundant with the tool name but keeps the sentence from bloating.

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, no-annotation, no-output-schema tool the description is minimally adequate: it compensates for the missing output schema by naming task id, status and output URLs. It leaves the polling/callback and parameter-role story unexplained, which matters given the required prompt/source_video_url pair.

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%, above the high-coverage threshold, so baseline is 3. The description adds no parameter-level meaning (prompt vs source_video_url, wait/timeout_ms interplay, aspect_ratio choices) beyond the schema's own text.

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 Runway Aleph task on RunAPI') plus the intent '(edit video)', so the agent knows this submits a video-editing job. It doesn't explicitly contrast with siblings get_task/check_pricing/login, but those are far enough apart that differentiation is obvious.

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?

No when-to-use context at all: nothing about when to prefer this over other task-creating calls, nothing about async polling vs callback_url, and no mention that results must later be fetched via get_task. The agent must infer the whole workflow.

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