Skip to main content
Glama

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

Create a Gen-4.5 video

runway_create_gen4_5

Generate a Runway Gen-4.5 video through its own route: text-to-video (16:9) from text_prompt, or image-to-video from a first-frame image asset (firstImage_assetId) with an optional prompt, 5, 8 or 10 s. runway_create_video with model gen4.5 runs the same model with any length from 2 to 10 s and an audio switch, and covers every other model: prefer it for new work. 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 /gen4_5/create.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "runway_create_gen4_5"
  }
}

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.
emailNoThe Runway account to run it on; an explicit email overrides the account that holds firstImage_assetId, otherwise that account runs it: its email from runway_list_accounts. Omit to let the API pick one of your accounts.
maxJobsNoOverride the account's maxJobs (Runway tasks at once) for this request, 1-10. Default: the account's own setting.
secondsNoVideo length in seconds: 5 (default), 8 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_promptNoWhat the video shows. Required for text-to-video (no firstImage_assetId), optional with an image.
aspect_ratioNoImage-to-video only (text-to-video is always 16:9). Default 16:9.
firstImage_assetIdNofirstImage_assetId, the image for the first frame; turns on image-to-video: 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.5/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the ~50 s wait, the return contract (video url and assetId, failure reason, or taskId for runway_get_task), credit consumption versus exploreMode, and the underlying POST route. It does not discuss failure retry behavior or what happens when the wait times out beyond returning a taskId, which keeps it short of a 5.

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 two generation modes before the sibling routing advice, so the most decision-relevant information comes first. It is a single dense, comma-chained sentence, which makes it harder to scan than a short structured list would be.

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

Completeness4/5

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

With 11 optional parameters and no output schema, the description carries the return contract, credit cost, and timeout behavior, which is what an agent needs to invoke and interpret it. Minor gaps remain around how email and maxJobs interact with account selection, though the schema documents those individually.

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 already 100%, so the baseline is 3; the description adds real meaning by explaining the mode switch between text_prompt and firstImage_assetId and noting that text-to-video is locked to 16:9 while aspect_ratio only applies to image-to-video. Account-selection semantics for email and maxJobs are left entirely to 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.5 video") and enumerates the two modes: text-to-video at 16:9 from text_prompt, or image-to-video from firstImage_assetId with an optional prompt. It explicitly distinguishes itself from the similarly named runway_create_video by naming that sibling and the capabilities it adds.

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?

Gives an explicit routing rule: runway_create_video handles gen4.5 with 2–10 s lengths and an audio switch plus every other model, and the description says to "prefer it for new work." That leaves this tool's niche (fixed 5/8/10 s lengths, its own route) unambiguous for an agent choosing among siblings.

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