Skip to main content
Glama

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

Delete a song

minimax_delete_music
DestructiveIdempotent

Delete one song or reference track from its MiniMax account by musicId; its audio_url stops working, so download it first. A song still rendering cannot be deleted (409): wait until minimax_get_music shows statusFinal true. The account comes from the musicId. Cannot be undone. DELETE /music/{musicId}.

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": {
      "musicId": "<musicId>"
    },
    "name": "minimax_delete_music"
  }
}

Input Schema

NameRequiredDescriptionDefault
musicIdYesThe musicId to delete, e.g. user:12345-minimax:123456789012345678-music:987654321098765 (it names the account).

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations (destructive, idempotent) by disclosing the side effect on audio_url, the irreversibility ('Cannot be undone'), the specific failure mode with its status code (409 for a rendering song), and the remedy. It also explains that the account is derived from the musicId rather than passed as a parameter.

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?

Three dense sentences, front-loaded with the action and its key, then the destructive side effect, then the blocking condition. Every clause carries operational information; nothing is padding.

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?

A one-parameter, no-output-schema delete tool whose annotations already carry the safety profile. The description covers the side effects, the failure case, and the account-resolution behavior, leaving nothing an agent needs in order to call it correctly.

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% and the only parameter's schema description already carries the example and the note that the musicId names the account, so the description's repetition adds little. Baseline 3 applies when 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?

States a specific verb and resource — delete one song or reference track — plus the key, musicId, and the endpoint DELETE /music/{musicId}. That is clearly distinguishable from the sibling deletes for files, images, speech, video, and voice.

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?

Gives concrete preconditions: download the audio first because audio_url stops working, and do not attempt deletion while a song is still rendering (wait for statusFinal true on minimax_get_music). It does not explicitly name alternatives, but for deletion of a music asset there is none in the catalog, so the guidance is effectively complete.

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