Skip to main content
Glama

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

List text-to-speech voices

pixverse_list_speech_voices
Read-onlyIdempotent

The text-to-speech voices of one model's provider for pixverse_create_speech: voice_id, display_name, gender, age, accent, recommended languages, preview_url and compatible_models; language narrows it to voices recommended for that language. A page at a time (offset, limit). Lip-sync voices are pixverse_list_lipsync_voices. GET /speech/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_speech_voices"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoThe PixVerse account email, as pixverse_list_accounts shows it. Required when more than one account is configured.
limitNoItems per page (default 50).
modelNoDefault speech-2.8-hd; the provider comes from it.
offsetNoWhere the page starts (default 0): the next_offset of the previous page.
languageNoA language code (en, es, ja, …); default auto.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description focuses on added context: results are paginated a page at a time via offset/limit, and the provider is derived from the chosen model. It also discloses the underlying endpoint (GET /speech/voices). It does not cover rate limits or whether an empty voice list for a language is possible, but the behavioral picture is solid for a read-only listing.

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?

A single dense sentence front-loads the resource, then the returned fields, then the pagination and alternative-tool pointers. No filler words; every clause carries information an agent would otherwise have to guess.

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?

There is no output schema, so listing the returned fields and explaining pagination is exactly the compensating detail needed. Combined with the 100%-covered input schema and read-only annotations, an agent has everything required to call it correctly.

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%, so the schema already documents all five parameters, and the baseline is 3. The description adds some meaning beyond the schema — that language filters to voices 'recommended for that language' and that model determines the provider — but repeats pagination and field semantics that the schema already conveys.

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 — the text-to-speech voices of one model's provider — and enumerates exactly what each entry contains (voice_id, display_name, gender, age, accent, languages, preview_url, compatible_models). It also names the closely related sibling it is not (pixverse_list_lipsync_voices) and the downstream consumer (pixverse_create_speech), so an agent can distinguish it without opening another schema.

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?

Implies the primary use case explicitly: this is the voice catalog feeding pixverse_create_speech, and lip-sync voices live elsewhere. It also explains that the language parameter narrows results to recommended voices. It stops short of stating exclusions such as when to omit the model filter versus when to query per-model, but the routing context is clear.

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