Skip to main content
Glama

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

Get speech

minimax_get_speech
Read-onlyIdempotent

One speech recording by audioId (from minimax_create_speech) or audio_id (from minimax_list_speech): statusLabel (pending, processing, completed, failed), statusFinal and, once completed, audio_url (MP3), text, model, voice_info, settings and cost_credit (the credits MiniMax charged); a failure's code and error. wait: true waits up to ~50 s for an unfinished one. An audioId from minimax_create_speech resolves for 7 days; after that find the recording with minimax_list_speech. GET /speech/{audio_id}.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "audio_id": "<audio_id>"
    },
    "name": "minimax_get_speech"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNoWait up to ~50 s for the job to finish (default false: one read).
audio_idYesThe audioId from minimax_create_speech, or an audio_id from minimax_list_speech, e.g. user:12345-minimax:123456789012345678-audio:… (it names the account).

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavior: the 7-day resolution window for audioIds, the ~50 s wait ceiling, the statusLabel progression (pending/processing/completed/failed), and the failure code/error path. It stops short of noting rate limits or whether cost_credit is billed on read, but the safety and lifecycle profile is well covered.

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-loads the identifier and source tools, then the returned fields, then the wait semantics and expiry rule in one dense but well-ordered paragraph. Every clause carries information an agent needs, 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?

With no output schema, the description compensates by enumerating the return fields (statusLabel, statusFinal, audio_url, text, model, voice_info, settings, cost_credit) and the failure shape. Combined with the expiry and wait rules, an agent has everything needed to call it correctly.

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; the description still adds meaning beyond the schema by explaining that the audioId is account-qualified and expires after 7 days, and that wait polls for up to ~50 s rather than just flagging a boolean.

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 ('One speech recording by audioId ... or audio_id') and explicitly ties both accepted identifiers to the sibling tools that produce them (minimax_create_speech, minimax_list_speech). The GET /speech/{audio_id} endpoint mapping removes any ambiguity about what is fetched vs. what the other sibling tools do.

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 routes the agent: use the audioId from minimax_create_speech while it resolves, and after 7 days 'find the recording with minimax_list_speech'. It also states when to set wait: true (unfinished job, ~50 s budget) versus the default single read.

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