Skip to main content
Glama

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

List lip sync voices

runway_list_lipsync_voices
Read-onlyIdempotent

List the voices Runway offers for lip sync and voice swap, live from the account: each voice's voiceId, name, labels (accent, age, gender, description, use case) and a sample MP3 url, all at once. Use it to pick the voiceId for runway_lipsync or runway_act_two_voice. GET /lipsync/voices.

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_list_lipsync_voices"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoThe Runway account to ask: its email from runway_list_accounts. Optional with one account, required with more.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. Beyond that the description adds genuinely useful behavior: the data is fetched live from the account rather than a static catalog, and every field including the sample MP3 url comes back in one call (implying no pagination or follow-up fetch).

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?

Two sentences plus the endpoint, front-loaded with the purpose and result shape before the usage pointer. Dense but every clause earns its place; the trailing 'GET /lipsync/voices' is minor overhead for an agent that cannot call HTTP directly.

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?

With no output schema, the description carries the return-value burden and does so fully by listing the fields returned. Combined with the annotations and a fully documented single parameter, an agent has everything needed to call it and use the result.

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 the single email parameter is already documented in the schema, including the 'optional with one account, required with more' rule. The description adds no parameter-level detail (for example, it does not restate the account-scoping constraint), so the baseline of 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 (list the lip sync / voice swap voices) plus the scope 'live from the account', and enumerates exactly what each record contains (voiceId, name, labels, sample MP3 url). That enumeration also distinguishes it from the sibling tools that consume a voiceId rather than return one.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly routes the agent: 'Use it to pick the voiceId for runway_lipsync or runway_act_two_voice', naming the two downstream consumers. It stops short of stating when-not to call it or any prerequisites, so it is clear context without full exclusion guidance.

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