runway-mcp

text_to_video

Create a Runway task on RunAPI to generate video from a text prompt, returning a task ID, status, and output URLs.

Instructions

Create a Runway task on RunAPI (text 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`	Yes	Declared type: string.
`watermark`	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`	Yes	Declared type: integer. Known values: 5, 10.
`poll_interval_ms`	No
`output_resolution`	Yes	Declared type: string. Known values: "720p", "1080p".
`first_frame_image_url`	No	Declared type: string.

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 / 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. Known values: 5, 10."
```
- removedInput schema / properties / duration_seconds / enum
```
Removed value: -[
-  5,
-  10
-]
```
- 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: -[
-  "runway"
-]
```
- 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 / timeout_ms / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / watermark / description
```
Added value: +"Declared type: string."
```

Changed5 schema fields changedv0.1.7Aug 5, 2026

addedInput schema / properties / callback_url
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / first_frame_image_url / type
```
Added value: +"string"
```
addedInput schema / properties / prompt / type
```
Added value: +"string"
```
addedInput schema / properties / watermark
```
Added value: +{
+  "type": "string"
+}
```

changedInput schema / required

Previous value: -[
-  "duration_seconds",
-  "output_resolution"
-]New value: +[
+  "prompt",
+  "duration_seconds",
+  "output_resolution"
+]

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?

No annotations are provided, so the description carries the full burden. It usefully discloses the return shape (task id, status, output URLs) and that this spawns an asynchronous task, which is meaningful context. However, it omits permissions, cost/credit implications, and the fact that parameters like wait, timeout_ms, and callback_url make this a long-running or callback-driven operation.

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 no filler, and the core action is front-loaded before the return-value note. It is efficient, though very terse for a tool with 11 parameters.

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?

There is no output schema, so the description reasonably explains the return values, which helps. But for a complex 11-parameter async generation tool it omits auth needs, cost implications, and routing versus its siblings, leaving genuine gaps.

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 high at 82%, so the schema already documents most parameters, establishing a baseline of 3. The description names none of the 11 parameters and adds no syntax or format detail beyond the schema, so it does not exceed the baseline.

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 clear verb and resource: 'Create a Runway task on RunAPI (text to video).' The 'text to video' qualifier distinguishes it from the extend_video sibling, which implies extending existing footage. It stops short of explicitly naming the alternative, so it lands at 4 rather than 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?

The description gives no when-to-use context, no prerequisites, and no mention of alternatives. With siblings like extend_video and get_task present, an agent gets no signal about which tool applies to a given request. It only describes the artifact created, not when to reach for it.

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