Skip to main content
Glama

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

List speech

minimax_list_speech
Read-onlyIdempotent

List one MiniMax account's speech recordings, newest first (made with the API or on minimax.io): audio_id, audio_title, text, voice_name, audio_url and whether SRT or WAV renditions exist, a page at a time; when has_more is true pass the next page number. cost_credit, model and voice settings are only on minimax_get_speech. GET /speech.

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

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.
page_sizeNoRecordings per page (default 100).

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and non-destructive behavior, yet the description adds ordering (newest first), page-by-page delivery, the has_more continuation rule, and which fields are deliberately omitted. It stops short of stating empty-result behavior or any rate/limit constraints, so it is strong but not exhaustive.

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?

It is a single dense sentence that front-loads the action and scope before the field list and the sibling routing. Every clause carries information, though the run-on structure and appended 'GET /speech' make it slightly harder to scan than it could be.

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, the description takes on the job of describing return values and does so by naming the fields and the has_more flag, plus how to continue paging. It omits edge cases like exhausting pages or an empty account, which is a modest gap for a simple read-only list tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema cannot: it ties the page parameter to the returned has_more flag, making the paging loop explicit. The account parameter's multi-account requirement is already in the schema, so the description only reinforces it.

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 definition states a specific verb and resource ('List ... speech recordings'), plus scope ('one MiniMax account's', 'newest first') and origin ('made with the API or on minimax.io'). It also enumerates the returned fields and explicitly distinguishes itself from minimax_get_speech, so an agent can separate the two 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?

It routes the agent to the alternative for detail fields ('cost_credit, model and voice settings are only on minimax_get_speech') and gives pagination guidance ('when has_more is true pass the next page number'). It does not spell out exclusions such as create/delete operations, but the list-vs-get split is the decision that matters here.

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