Skip to main content
Glama

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

List songs

minimax_list_music
Read-onlyIdempotent

List one MiniMax account's music, newest first, including songs made on minimax.io and tracks still rendering: musicId, title, statusLabel, duration, audio_url, typeLabel (song or reference) and referenceMusicId for covers. type picks songs (default), references or all. Page with lastMusicId (the last musicId of the previous page). minimax_get_music reads one song. GET /music.

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_list_music"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNosong (generated songs, covers included; default), reference (uploaded reference tracks) or all.
limitNoSongs to return, 1-100 (default 30).
accountNoThe MiniMax account id (minimax_list_accounts) to list. Required when you have several MiniMax accounts; with one it may be left out.
favoriteNotrue: only songs marked as favourites on the MiniMax account. Default false.
lastMusicIdNoThe musicId to continue after (the last one of the previous page); looked up among the most recent 1000 songs, older answers 400, 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.1/5.0
Behavior4/5

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

Annotations already declare this a read-only, idempotent, non-destructive open-world call, so the safety profile is covered. The description still adds genuine behavior: results are ordered newest first, include still-rendering tracks, and covers carry referenceMusicId — details not derivable from annotations.

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?

Front-loaded with the core action and scope, then field list, then filtering and paging notes. It is dense but largely waste-free; the field enumeration earns its place because there is no output schema, though the trailing 'GET /music' is near-redundant.

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 compensates by listing returned fields and the cover/reference linkage, and it covers ordering, rendering-state inclusion and pagination. Multi-account handling is only implied ('one MiniMax account's music') even though the account parameter is optional when a single account exists.

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%, so the schema already documents type, limit, account, favorite and lastMusicId. The description mostly restates these ('type picks songs (default), references or all', 'lastMusicId (the last musicId of the previous page)') without adding format or edge-case meaning beyond the schema, so baseline 3 applies.

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?

Names a specific verb and resource ('List ... music') plus scope ('one MiniMax account's music, newest first') and enumerates the returned fields. It explicitly contrasts with the sibling reader ('minimax_get_music reads one song'), so an agent can distinguish the two 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context: use it for paging through an account's library, use minimax_get_music for a single song, and use type=newest-first paging via lastMusicId. It lacks an explicit 'when not to use' (e.g., search by title or filter by date), so it is strong but not fully routing.

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