Skip to main content
Glama

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

Upload a voice sample

minimax_upload_voice_sample

Upload one audio sample (MP3 or WAV, 10 to 60 seconds of speech, up to 50 MB through this server) to an account for voice cloning. Returns a fileID; pass up to 10 fileIDs from the same account to minimax_clone_voice. Not for music covers: use minimax_upload_music_reference. POST /speech/upload-sample.

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

Input Schema

NameRequiredDescriptionDefault
urlNoA public https URL of the audio file.
accountNoThe MiniMax account id (minimax_list_accounts) to upload to (the voice is cloned there). Required when you have several MiniMax accounts; with one it may be left out.
mimeTypeNoThe file's type. Default: from the url's answer.
contentBase64NoThe file content, base64-encoded (instead of url; small files).

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-idempotent, non-destructive and open-world behavior, so the description's job is to add context — which it does: return value (a fileID), the per-account limit of 10 samples, the 10–60s speech / 50 MB constraints, and the account-scoping rule. It stops short of stating auth requirements, whether re-uploads are deduplicated or what happens to a rejected sample, 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?

Three tight sentences: capability plus constraints first, workflow hand-off second, exclusion third. Nearly every clause carries information; the trailing "POST /speech/upload-sample" is implementation trivia that an agent cannot act on, which is the only real waste.

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, and the description compensates by naming the return value (fileID) and its downstream use. Combined with the size/duration limits, the account scoping and the explicit sibling exclusion, an agent has everything needed to call this correctly and route the result.

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%, so all four parameters (url, account, mimeType, contentBase64) are already documented in the schema, and the description largely restates them. It adds only marginal semantics — the 50 MB server-side limit relevant to choosing contentBase64 over url, and the 'same account' constraint tying account to downstream clone calls. Baseline 3 is appropriate.

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?

Opens with a specific verb and resource ("Upload one audio sample") and immediately bounds it with format, duration and size limits. It also names the sibling it is not (minimax_upload_music_reference) and the sibling it feeds into (minimax_clone_voice), so the agent can place it in a workflow without opening either schema.

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?

Gives explicit positive guidance (pass up to 10 fileIDs from the same account to minimax_clone_voice), an explicit exclusion with the correct alternative ("Not for music covers: use minimax_upload_music_reference"), and an upstream reference (minimax_list_accounts via the account param). Both when-to-use and when-not-to-use are covered.

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