Skip to main content
Glama

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

List text-to-speech models

pixverse_list_speech_models
Read-onlyIdempotent

The text-to-speech models by provider, live from PixVerse: model, display_name, max_characters, supported_language_codes and credit_formula (credits per unit of characters), plus default_model. Use it to pick a model and language_code for pixverse_create_speech; voices come from pixverse_list_speech_voices. GET /speech/models.

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

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.4/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 safety profile is covered; the description adds that the data is live from PixVerse and lists the returned fields (useful since there is no output schema). It does not discuss pagination, caching, or failure modes, so it falls short of fully rich behavioral disclosure.

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 resource, then the returned fields, then the routing guidance. Two dense sentences with no filler; even the trailing endpoint path is short and aids traceability.

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

Completeness4/5

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

With no output schema, describing the returned fields is exactly the right compensating detail, and the account-selection caveat is handled by the schema. Close to complete for a simple read-only list tool, with only minor gaps around ordering or result-size behavior.

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 the email parameter, 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 (list) and resource (text-to-speech models) and enumerates exactly what each entry contains: model, display_name, max_characters, supported_language_codes, credit_formula, default_model. It also distinguishes itself from the sibling voices tool, so an agent can tell immediately this is the model/metadata catalog, not a voice catalog.

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?

Explicitly says 'Use it to pick a model and language_code for pixverse_create_speech' and routes voice selection to pixverse_list_speech_voices. That is a concrete when-to-use plus a named alternative with the condition that selects 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