Skip to main content
Glama

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

Animate a character (Act-Two)

runway_act_two

Animate a character with Runway Act-Two: a driving performance video (3-30 s) moves a character given as an image or video asset, with optional body control and expression intensity. For motion transfer with Kling use runway_create_video (model kling-3.0-motion-control); to change only the voice of a video use runway_act_two_voice. 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/act-two.

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": {
      "driving_assetId": "<driving_assetId>",
      "character_assetId": "<character_assetId>"
    },
    "name": "runway_act_two"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedNoSeed for reproducible results, 1-2147483647; 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.
aspect_ratioNoOutput shape. Default 16:9.
body_controlNoTrack body movement as well as the face (default true).
driving_assetIdYesdriving_assetId, the performance video (3-30 s): 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.
character_assetIdYescharacter_assetId, the character as an image or video asset: 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.
expression_intensityNoFacial expression intensity, 1-5 (default 3).

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, open-world, non-idempotent, non-destructive operation, and the description goes further by disclosing the ~50 s wait window, the four possible outcomes (video url/assetId, failure reason, taskId), credit consumption and the exploreMode no-credit path, plus the underlying POST /gen4/act-two endpoint. The only modest gap is that it does not discuss what happens to existing assets or retry behavior on failure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and mechanism come first, sibling routing second, and return/credit semantics last, with no filler. Every clause carries actionable information: duration limits, asset sources, wait behavior, alternatives, and endpoint.

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 10-parameter generative task with no output schema, the description covers the return shapes, the async fallback path, the cost model, and where asset IDs come from. Nothing an agent needs in order to select or call this tool correctly is missing.

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 a baseline of 3 applies, but the description adds meaning beyond the schema by framing driving_assetId as a performance clip constrained to 3-30 s and character_assetId as an image or video asset, and by tying body_control and expression_intensity to the animation result. It does not add format or syntax detail beyond what the schema already provides for seed, replyUrl or aspect_ratio.

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?

The description states a specific verb and resource ('Animate a character with Runway Act-Two') and explains the mechanism: a 3-30 s driving performance video moves a character supplied as an image or video asset. It also names the sibling tools it is not (runway_create_video with kling-3.0-motion-control, runway_act_two_voice), so an agent can distinguish it without opening any schema.

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?

It gives explicit routing rules: use runway_create_video with the Kling motion-control model for motion transfer, and runway_act_two_voice when only the voice should change. It also explains the wait-mode branch (taskId returned for runway_get_task) and the credits/exploreMode trade-off, which covers when and how to invoke it.

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