Skip to main content
Glama

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

Swap the voice of a video

runway_act_two_voice

Replace the voice in a video (3-30 s) with one of Runway's voices (Act-Two voice swap), keeping the picture. Pick a voiceId with runway_list_lipsync_voices. To make a face speak new words use runway_lipsync; to animate a character use runway_act_two. 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-voice.

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>",
      "voiceId": "<voiceId>"
    },
    "name": "runway_act_two_voice"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNoWait up to ~50 s for the task to finish (default true); false returns the taskId at once.
voiceIdYesThe voice to use: a voiceId from runway_list_lipsync_voices.
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.
video_assetIdYesvideo_assetId, the video (3-30 s) whose voice to swap: 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.1/5.0
Behavior3/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), and the description adds genuinely useful behavior: the ~50 s wait window, the returned url/assetId, the failure reason and taskId fallback, credit consumption, and that the task runs on the account holding the asset. It stops short of stating permissions, reversibility, or rate limits, so it adds context but not a full behavioral contract.

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?

Front-loaded with the action and constraint, then alternatives, then return semantics and endpoint. No redundant sentences; the routing and outcome information is packed without waste.

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

Completeness3/5

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

No output schema exists, and the description fills that gap by naming the return values (url, assetId, failure reason, taskId) and the get-task handoff. For a credit-spending mutation tool it still omits permission requirements and failure-recovery detail, leaving a modest gap.

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%, with every parameter including wait, exploreMode, replyUrl and video_assetId already documented in the schema. The description only reinforces voiceId sourcing and the wait/taskId outcome, adding little meaning beyond the structured fields, so the baseline 3 applies.

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 ("Replace the voice in a video") plus a hard constraint (3-30 s) and keeps the picture. It explicitly separates itself from runway_lipsync (new words) and runway_act_two (animate a character), so an agent can route without opening schemas.

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 alternatives with the condition that selects them: use runway_lipsync to make a face speak new words, runway_act_two to animate a character, and runway_list_lipsync_voices to obtain a voiceId. Also flags when credits are spent versus exploreMode.

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