Skip to main content
Glama

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

Get a song

minimax_get_music
Read-onlyIdempotent

One song from minimax_create_music, or a reference from minimax_upload_music_reference, by musicId: statusLabel (pending, processing, completed, failed, moderated), statusFinal and, once completed, audio_url (MP3), duration, title, lyrics and model; typeLabel tells a song from a reference, referenceMusicId marks a cover. wait: true waits up to ~50 s for an unfinished song. minimax_list_music lists many. GET /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_get_music"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNoWait up to ~50 s for the job to finish (default false: one read).
musicIdYesThe musicId of a song or reference, 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?

Annotations already cover readOnly/idempotent/non-destructive, and the description goes well beyond them by enumerating the statusLabel lifecycle (pending, processing, completed, failed, moderated), stating that audio_url, duration, title, lyrics and model only materialize once completed, and distinguishing songs from references via typeLabel/referenceMusicId. It also discloses the ~50 s wait ceiling, which is real behavioral context an agent needs to avoid double-polling.

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?

Purpose and provenance are front-loaded in the first clause, followed by return shape, the wait behavior, and the list alternative in a logical order. It is dense — one long semicolon-chained sentence — but nearly every clause carries information, with only slight redundancy between the description's wait note and the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 must shoulder the return-value burden, and it does so by naming the fields, their type (MP3), and when they appear, plus the status enumeration. It falls just short of full completeness by omitting behavior on invalid or deleted musicIds and whether 'wait' can be repeated across multiple calls.

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%, so both parameters (musicId format with account naming, and wait with its ~50 s default-false behavior) are already documented in the schema. The description restates the wait semantics and adds only the qualifier 'for an unfinished song', so it does not substantially extend parameter meaning beyond the structured data.

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 names a specific verb and resource ('One song ... by musicId') and immediately traces provenance to the two sibling tools that produce the object (minimax_create_music, minimax_upload_music_reference), so an agent can distinguish it from minimax_list_music or the create/upload paths 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?

It routes the agent explicitly: use this for a single song by id, use minimax_list_music to list many, and set wait: true when polling an unfinished job versus the default single read. The only mild gap is that no failure/not-found path is described, but the when/when-not/alternative guidance is otherwise 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