Skip to main content
Glama

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

Upload a reference track

minimax_upload_music_reference

Upload an audio file (MP3 or WAV, up to 50 MB through this server) to one MiniMax account as a reference track for covers. Returns its musicId, ready at once, and the lyrics MiniMax transcribed from it (pass them as lyrics to keep the original words). A reference is a permanent record on the account, reusable for any number of covers: upload once and pass the musicId as referenceMusicId to minimax_create_music. Uploading costs no credits; a song already on the account needs no upload. POST /music/reference.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "minimax_upload_music_reference"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoA public https URL of the audio file.
nameNoThe title the reference is stored under, max 40 characters. Default: a timestamp.
accountNoThe MiniMax account id (minimax_list_accounts) to store the reference on (covers of it run there). Required when you have several MiniMax accounts; with one it may be left out.
mimeTypeNoThe file's type. Default: from the url's answer.
contentBase64NoThe file content, base64-encoded (instead of url; small files).

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint false, openWorldHint true), the description discloses that the upload costs no credits, that the reference is ready immediately with no polling, that it is a permanent reusable record, and that the response includes both musicId and transcribed lyrics. These are operational facts an agent would otherwise have to discover by trial.

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?

The lead sentence front-loads format, size limit, and purpose, and the following sentences each contribute new information without padding. The last two clauses ('upload once and pass...' and the endpoint) are slightly dense but still earn their place.

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 write tool with no output schema, the description covers format and size constraints, cost, synchronous return values, how the result is reused downstream, and multi-account handling. An agent could call this correctly and know what to do with the response without further queries.

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 the schema already documents every parameter including the url/contentBase64 and account alternatives. The description adds workflow meaning (musicId to reuse, lyrics to pass back) but no per-parameter detail beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource -- upload an audio file as a 'reference track for covers' -- and states the accepted formats (MP3/WAV) and the 50 MB server limit. It doesn't explicitly name the closest sibling (minimax_upload_file) to say how this differs from a generic file upload, so it falls just short of full sibling differentiation.

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 states when to use it (to build a reusable reference for covers), what to do afterwards (pass the returned musicId as referenceMusicId to minimax_create_music), and when not to bother ('a song already on the account needs no upload'). The when/when-not pair and the downstream alternative are both explicit.

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