Skip to main content
Glama

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

Clone a voice

minimax_clone_voice

Build a new voice from 1-10 samples uploaded with minimax_upload_voice_sample (same account). Takes a cloned voice slot (minimax_get_voice_quota shows them; out of slots is an error). Returns the voice_id to pass to minimax_create_speech, voice_name, tag_list and a sample_audio URL. Cloned voices are listed by minimax_list_voices with is_system false. POST /speech/clone-voice.

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": {
      "files": "<files>",
      "voice_name": "<voice_name>",
      "language_tag": "<language_tag>"
    },
    "name": "minimax_clone_voice"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesYesThe fileIDs from minimax_upload_voice_sample, 1-10; each sample 10 to 60 seconds long. They name the account.
voice_nameYesThe new voice's name, 1-30 characters.
language_tagYesThe voice's language: a tag_name from voice_tag_language of minimax_get_speech_config, e.g. English.
need_noise_reductionNoRemove background noise from the samples (default true).

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare it is a non-destructive, non-idempotent write; the description adds what those annotations cannot — that the call consumes a cloned-voice slot, that slot exhaustion surfaces as an error, and what the response contains (voice_id, voice_name, tag_list, sample_audio URL). The underlying endpoint is also disclosed, which helps an agent reason about failure modes.

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?

Front-loaded with the core action and prerequisite, then return values, then lifecycle guidance, with no filler sentences. The telegraphic fragment style (

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 carries the burden of describing the return payload and does so (voice_id, voice_name, tag_list, sample_audio URL). Prerequisites, quota constraints and follow-up calls are all covered, so an agent can invoke it correctly without further context.

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 files, voice_name, language_tag and need_noise_reduction are already documented. The description reinforces provenance for files (fileIDs from the upload tool, account-scoped) but adds little beyond that, so the baseline 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 ("Build a new voice") plus the scope ("from 1-10 samples"), and distinguishes itself from siblings by naming the prerequisite upload tool and the downstream consumers of the returned voice_id.

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 sequences the workflow: samples must come from minimax_upload_voice_sample, a free cloned-voice slot is required (checkable via minimax_get_voice_quota), and exhausting slots is an error. It also routes the agent forward to minimax_create_speech and minimax_list_voices.

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