Skip to main content
Glama

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

Delete a cloned voice

minimax_delete_voice
DestructiveIdempotent

Delete one cloned voice by its voice_id (from minimax_clone_voice or minimax_list_voices with is_system false), freeing its slot. The account comes from the voice_id. Answers success for a voice that does not exist or is already deleted. Cannot be undone. POST /speech/delete-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": {
      "voice_id": "<voice_id>"
    },
    "name": "minimax_delete_voice"
  }
}

Input Schema

NameRequiredDescriptionDefault
voice_idYesThe cloned voice's voice_id, e.g. user:12345-minimax:123456789012345678-voice:… (it names the account).

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 declare destructive=true and idempotentHint=true, but the description adds genuinely new behavior: deleting a nonexistent or already-deleted voice still answers success (a silent no-op an agent must know about), the account is derived from the voice_id rather than a separate argument, and the action cannot be undone. It omits permission/auth requirements and the exact response payload, keeping it below 5.

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?

Four compact sentences, each carrying distinct information: what is deleted, where the id comes from, the silent-success edge case, and irreversibility. The irreversible warning is front-loaded before the endpoint, with zero 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?

For a single-parameter destructive tool with no output schema, the description covers the input source, the destructive/idempotent semantics with the tricky no-op success case, and the underlying endpoint. Nothing an agent needs in order to call it safely is missing.

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?

With one required parameter at 100% schema coverage, the schema already explains the voice_id format and that it names the account. The description mostly restates that, adding only the provenance (which sibling tools yield a valid id), so it is a marginal gain over the schema baseline of 3.

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 description opens with a specific verb and resource ('Delete one cloned voice by its voice_id') and immediately scopes it to cloned voices sourced from minimax_clone_voice or minimax_list_voices with is_system false, which tells an agent exactly which sibling produces the input and that system voices are out of scope.

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 names the two upstream tools that supply voice_id and the is_system false qualifier, which is clear context for when to call this. It stops short of an explicit 'do not use for system voices / use X instead' exclusion, so a 4 rather than 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