Skip to main content
Glama

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

List voices

minimax_list_voices
Read-onlyIdempotent

List the voices an account can speak with: MiniMax's built-in catalogue (default, filtered by tag_list and paged) or, with is_system false, your cloned voices (all at once). Each has voice_id (for minimax_create_speech), voice_name, tag_list and a sample_audio URL; has_more and total for paging. Tags come from minimax_get_speech_config. 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": "minimax_list_voices"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, from 1 (default 1).
accountNoThe MiniMax account id (minimax_list_accounts) to list. Required when you have several MiniMax accounts; with one it may be left out.
tag_listNoOnly voices with these tags, e.g. ["Italian", "Female"]: tag_name values from minimax_get_speech_config.
is_systemNotrue (default): built-in voices; false: voices cloned with minimax_clone_voice (page and page_size are ignored).
page_sizeNoVoices per page (default 50 here).

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 establish readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds real behavior beyond that: is_system=false ignores page and page_size and returns everything at once, page_size defaults to 50 here, and responses carry has_more and total for paging plus a sample_audio URL. Only the account-resolution behavior (required when multiple accounts exist) is left to the schema.

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?

Three dense sentences, front-loaded with the account/catalogue scope, followed by return shape and input provenance. Every clause carries information, though the sentence packing makes it slightly harder to scan than a bulleted or shorter phrasing, and the trailing 'GET /speech/voices' is marginal value.

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 compensates by listing the returned fields (voice_id, voice_name, tag_list, sample_audio) and the paging envelope (has_more, total). Combined with five optional parameters and a default-mode explanation, an agent has everything needed to call this correctly on the first attempt.

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 explains page, account, tag_list, is_system and page_size, including the cloned-voice paging exception and the tag_name source. The description restates the same semantics rather than adding new detail such as page_size caps or tag matching behavior, 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 voices an account can speak with) and immediately splits the two operating modes: built-in catalogue by default vs cloned voices with is_system=false. It also names the return fields, so an agent can tell it apart from minimax_list_speech and minimax_get_voice_quota without opening a 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?

Gives concrete conditions: default mode is the filtered/paged built-in catalogue, is_system=false returns cloned voices all at once. It also routes the agent to sibling tools for inputs (tags from minimax_get_speech_config) and downstream use (voice_id for minimax_create_speech). It does not explicitly say when to prefer this over nearby list tools such as minimax_list_speech, which keeps it below a 5.

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