Skip to main content
Glama

Runway MCP Server by useapi.net (third-party)

Create a Gen-4 Turbo video

runway_create_gen4_turbo

Generate a Runway Gen-4 Turbo video from a first-frame image asset (required) and an optional prompt, 5 or 10 s, through its own route; the account that holds the image runs it. runway_create_video with model gen4-turbo does the same through the general route that covers every model (prefer it for new work); runway_create_gen4 is the standard Gen-4. Waits up to ~50 s, then returns the video url and assetId, the failure reason or the taskId for runway_get_task. Uses credits, or none with exploreMode. POST /gen4turbo/create.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "firstImage_assetId": "<firstImage_assetId>"
    },
    "name": "runway_create_gen4_turbo"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedNoSeed for reproducible results, 1-4294967294; random when omitted.
waitNoWait up to ~50 s for the task to finish (default true); false returns the taskId at once.
secondsNoVideo length in seconds: 5 (default) or 10.
replyRefNoYour own reference id, stored and returned with the task.
replyUrlNoA callback URL the API calls with the task (the runway_get_task shape) when it completes or fails. Default: the replyUrl of your useapi.net account.
exploreModeNoExplore Mode: true spends no credits and runs at lower priority; only for accounts on a Runway Unlimited plan. Omit or false: Credits Mode.
text_promptNoDescribe the shot (optional).
aspect_ratioNoDefault 16:9.
firstImage_assetIdYesfirstImage_assetId, the image for the first frame: an assetId from runway_upload_asset, runway_list_assets or a finished task (runway_get_task artifacts). The task runs on the Runway account that holds the asset.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnly=false, destructive=false, openWorld=true and non-idempotent, so the safety profile is known. The description adds genuinely useful context beyond that: the ~50 s wait, the returned url/assetId/failure reason/taskId, that credits are spent, and that the task runs on the account holding the image. It lacks detail on what happens to credits on a failed task, which keeps it below a 4-5 given how much is already covered by annotations.

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?

Front-loaded with the core action and requirement, then alternatives, then behavior. Dense and semicolon-heavy, but nearly every clause carries routing or behavioral information; a light trim would make it easier to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With nine parameters, no output schema, and a 50 s wait, the definition covers what an agent needs: input provenance, cost model, wait semantics, and the exact three possible return shapes mapped to runway_get_task. Nothing material is left to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% so the baseline is 3, but the description adds meaning the schema cannot: the account-ownership rule for firstImage_assetId and the provenance of assetIds (runway_upload_asset, runway_list_assets, runway_get_task artifacts). It also restates the 5/10 s and exploreMode semantics, which are already in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Generate a Runway Gen-4 Turbo video') plus the key constraint (first-frame image asset required, optional prompt, 5 or 10 s) and differentiates itself from two named siblings before any schema is opened. An agent can identify exactly what this produces.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: 'runway_create_video with model gen4-turbo does the same through the general route that covers every model (prefer it for new work)', and clarifies runway_create_gen4 is the standard Gen-4 variant. It also states the credit/exploreMode condition, so both selection and cost trade-offs are covered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources