Skip to main content
Glama

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

Edit a video with Aleph

runway_edit_video_aleph

Transform an existing video with Runway Gen-4 Aleph (video-to-video): a video asset plus a text prompt describing the change or style, optionally guided by an image asset. Use it to restyle or alter footage you have; to make a new video use runway_create_video, to edit with Kling O3 or Seedance 2.5 use runway_create_video (videoAssetId, video_mode). 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/video.

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": {
      "video_assetId": "<video_assetId>",
      "text_prompt": "<text_prompt>"
    },
    "name": "runway_edit_video_aleph"
  }
}

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.
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_promptYesThe transformation or style to apply.
image_assetIdNoimage_assetId, an optional image that conditions the result: 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.
video_assetIdYesvideo_assetId, the video to transform (it needs duration, width and height metadata): 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.2/5.0
Behavior3/5

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

The description adds substantial behavior beyond the annotations: a ~50 s wait with the return shape (video url and assetId, failure reason, or taskId for runway_get_task), credit consumption, and the exploreMode no-credit path. It also names the underlying POST /gen4/video endpoint. Annotations already cover the safety profile (readOnly=false, destructive=false, openWorld=true), and the description does not contradict them; the remaining gap is that it doesn't say what happens to the source video asset.

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-loads purpose, then alternatives, then return/cost behavior in a tight block with no filler. The sentence packing several sibling routings is dense but each clause carries distinct routing information.

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 an 8-parameter generative mutation with no output schema, the definition covers inputs, wait semantics, return values, cost model, and alternative tools. An agent can call it and handle the response correctly without further information.

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 coverage is 100%, so every parameter including wait, seed, replyUrl, and exploreMode is already documented in the schema. The description's mention of the optional image conditioning and the ~50 s wait largely restates the schema rather than adding new semantics; baseline 3 applies when the schema carries the load.

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 ("Transform an existing video with Runway Gen-4 Aleph (video-to-video)") and names the exact inputs involved: a video asset, a text prompt, and an optional image. It explicitly separates itself from runway_create_video for new videos and for Kling O3 / Seedance 2.5 edits.

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 explicit when-to-use (restyle or alter footage you already have) and when-not-to-use, routing to runway_create_video for new videos and for the Kling O3 / Seedance 2.5 video_mode path. Nothing about sibling selection is left to inference.

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