SunoMCP

suno_get_mp3

Convert any generated song to MP3 for compact, widely supported playback. Get a portable audio file smaller than WAV, ready to share across platforms.

Instructions

Get the MP3 format of a generated song.

Converts the song to MP3 format, which is compact and widely supported
across playback devices and platforms.

Use this when:
- You need a compressed and portable audio format
- You want to share songs easily across platforms
- You prefer smaller file sizes than WAV

Returns:
    Task ID and MP3 audio information.

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": "suno_get_mp3"
  }
}

Input Schema

Name	Required	Description	Default
`audio_id`	Yes	The song ID to get the MP3 format for.
`callback_url`	No	Webhook callback URL for asynchronous notifications.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.14Sep 4, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are present, so the description carries the behavioral burden. It discloses that conversion to MP3 occurs and that a Task ID plus MP3 audio info are returned, but it does not explain asynchronous behavior or callback semantics despite callback_url being 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?

Compact and well-organized with clear sections: what it does, when to use it, and what it returns. The wording is efficient and front-loaded with no filler.

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 an output schema present and full parameter documentation, the description provides enough context for basic invocation and selection. The main missing element is an explicit note about the asynchronous task lifecycle, though 'Task ID' implicitly hints at it.

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%, with both audio_id and callback_url already documented. The description adds no parameter-level meaning beyond the schema, so the 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?

Clearly states it gets/converts a generated song to MP3 format, with explicit compression and portability rationale. The format-specific focus distinguishes it from sibling tools like suno_get_wav, suno_get_mp4, and suno_get_midi.

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?

Provides a concrete 'Use this when' list covering compressed audio needs, sharing, and smaller file sizes. It does not explicitly name sibling alternatives or exclusion cases, which is the only gap preventing a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server