Skip to main content
Glama

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

Create a Gen-4 video

runway_create_gen4

Generate a Runway Gen-4 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 does the same through the general route that covers every model (prefer it for new work); runway_create_gen4_turbo is the Gen-4 Turbo route. 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/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"
  }
}

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
Behavior4/5

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

Beyond the annotations (openWorldHint, non-idempotent, non-destructive), it discloses the ~50 s wait window, what is returned (video url and assetId, failure reason, or taskId for runway_get_task), the credit cost and the exploreMode exception, and the underlying POST /gen4/create route. That is substantial cost and lifecycle context the annotations do not carry.

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?

One dense but front-loaded paragraph: purpose first, then routing alternatives, then return/credit behavior, then the endpoint. Every clause contributes, though the semicolon-chained style is packed enough to read as a run-on.

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?

For a 9-parameter generation tool with no output schema, the description covers required inputs, runtime behavior, cost model, return values, and failure recovery path via runway_get_task. Nothing an agent needs to call it correctly is missing.

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 100% and every parameter is documented in the schema itself, including the firstImage_assetId provenance and the exploreMode credit rule, so the description mostly restates it. Baseline 3 is appropriate since the schema does the heavy lifting.

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 Gen-4 video) plus the required input shape (first-frame image asset, optional prompt, 5 or 10 s) and explicitly distinguishes itself from runway_create_video with model gen4 and runway_create_gen4_turbo.

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?

Tells the agent to prefer runway_create_video's general route for new work and names the turbo sibling as a separate route, while also stating the precondition that the Runway account holding the asset runs the job. Both the when-to-use and the when-to-prefer-alternative guidance are explicit.

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