Skip to main content
Glama

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

Delete speech

minimax_delete_speech
DestructiveIdempotent

Delete one speech recording from its MiniMax account by audioId or audio_id; it leaves the account and minimax_list_speech. Answers success for a recording that does not exist or is already deleted. A generation still running cannot be deleted (400): wait until minimax_get_speech shows it final, then delete it. minimax_stop_tracking does not stop it and leaves this audioId undeletable; then delete the finished recording by its audio_id from minimax_list_speech. Cannot be undone. DELETE /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_delete_speech"
  }
}

Input Schema

NameRequiredDescriptionDefault
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
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds non-obvious behavior anyway: deleting a nonexistent or already-deleted recording still answers success, and the deletion is irreversible. It also discloses the 400 precondition for in-flight generations and the surprising side effect that stop_tracking can strand an audioId — details the annotations cannot convey.

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 verb and resource in the first clause, then layers failure modes in descending importance, ending with the endpoint. Every sentence carries a distinct, actionable fact — no filler or restatement of the title.

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 one-parameter destructive delete with no output schema, the definition covers success semantics, irreversibility, failure preconditions, and recovery paths. An agent has everything needed to call it correctly and to interpret the response.

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 description coverage is 100% and the single audio_id parameter is already documented with its format and provenance in the schema. The description restates the audioId/audio_id duality and that the id names the account, adding little beyond the structured field. Baseline 3 applies since the schema does the heavy lifting.

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?

Uses a specific verb+resource ("Delete one speech recording") and immediately pins the scope to the speech resource, which cleanly separates it from the other delete siblings (delete_file, delete_image, delete_music, delete_video, delete_voice). It even states the underlying endpoint DELETE /speech/{audio_id}, leaving no ambiguity about what object is mutated.

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 covers when the call fails and what to do instead: a generation still running cannot be deleted (400), so wait until minimax_get_speech shows it final. It also names a specific misuse path — minimax_stop_tracking does not stop the job and leaves the audioId undeletable — and routes the agent to recover via minimax_list_speech. That is genuine when/when-not/alternative guidance.

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