Skip to main content
Glama

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

List lip-sync voices

pixverse_list_lipsync_voices
Read-onlyIdempotent

The voices for lip-sync speech: speaker_id, display_name and a sample url. Pass a speaker_id to pixverse_lipsync_video (speaker_id) or pixverse_create_video (lip_sync_tts_speaker_id, v5). Text-to-speech voices are a different list: pixverse_list_speech_voices. GET /videos/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": "pixverse_list_lipsync_voices"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoThe PixVerse account email, as pixverse_list_accounts shows it. Required when more than one account is configured.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so safety is covered. The description adds value beyond that by disclosing the underlying GET endpoint, the shape of each returned voice entry, and the downstream consumption path for speaker_id, though it says nothing about pagination, ordering, or account scoping behavior.

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?

Three short sentences, each earning its place: what the list contains, where its IDs are consumed, and which sibling is the different list. The return fields and the alternative are front-loaded with no filler.

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 read-only lookup tool with no output schema, the description compensates by naming the three returned fields and the endpoint. Combined with 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 coverage is 100% and the single email parameter is fully documented in the schema, including the multi-account requirement. The description adds nothing about email, so this sits at the baseline where the schema carries the semantics.

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 names the exact resource (lip-sync speech voices), enumerates the returned fields (speaker_id, display_name, sample url), and explicitly separates it from the sibling list of text-to-speech voices. An agent can distinguish this from pixverse_list_speech_voices without opening either 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 states what to do with the output — pass speaker_id to pixverse_lipsync_video or to pixverse_create_video's lip_sync_tts_speaker_id (v5) — and names the wrong-list alternative with the condition that selects it. This is explicit when-to-use and when-not-to-use 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