Skip to main content
Glama

suno_stems_music

Separate a song into vocals and instrumental stems for remixing, karaoke, or isolating specific parts. Returns individual track URLs.

Instructions

Separate a song into individual stems (vocals and instruments).

Splits the audio into separate tracks for vocals and instrumentals,
useful for remixing, karaoke, or isolating specific parts.

Use this when:
- You want to separate vocals from instrumentals
- You need individual stem tracks for mixing
- You want to create a karaoke version

Returns:
    Task ID and stem separation results with individual track URLs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
audio_idYesID of the audio to separate into stems.
callback_urlNoWebhook callback URL for asynchronous notifications.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided, so description carries full burden. It describes the action (splits audio) and return format (Task ID and stem results with URLs), but does not disclose behavior like whether it is destructive, async nature (callback_url implies async), or any prerequisites.

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?

Description is front-loaded with purpose, then explains use cases, then returns. It is reasonably concise but could be slightly more streamlined by removing the redundant 'Separate a song' line.

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?

Given low complexity (2 params, simple action, output schema exists), the description covers purpose, usage, and return format adequately. It is complete enough for an agent to use 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%, so baseline 3. Description adds minimal value: it mentions return format but not parameter details. Schema already describes both parameters clearly.

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 clearly states the tool separates a song into stems (vocals and instruments). It specifies the resource (song) and the action (separate), and distinguishes from similar sibling tools like suno_extract_vocals by emphasizing multiple stems.

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 explicit 'Use this when' list with three clear scenarios (separating vocals, needing stems, karaoke). However, it does not explicitly state when not to use or compare to alternatives like suno_extract_vocals.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AceDataCloud/SunoMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server