Skip to main content
Glama

suno_stems_music

Separate any song into individual vocal and instrumental stems for remixing or creating karaoke versions.

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

Implementation Reference

  • The main handler function for the suno_stems_music tool. Decorated with @mcp.tool(), it takes an audio_id (and optional callback_url), calls client.generate_audio with action='stems', and returns the formatted result.
    @mcp.tool()
    async def suno_stems_music(
        audio_id: Annotated[
            str,
            Field(description="ID of the audio to separate into stems."),
        ],
        callback_url: Annotated[
            str | None,
            Field(description="Webhook callback URL for asynchronous notifications."),
        ] = None,
    ) -> str:
        """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.
        """
        result = await client.generate_audio(
            action="stems",
            audio_id=audio_id,
            callback_url=callback_url,
        )
        return format_audio_result(result)
  • main.py:210-213 (registration)
    Registration of suno_stems_music in the server card tool list (main.py HTTP route), listing the tool with a description for client discovery.
    {
        "name": "suno_stems_music",
        "description": "Separate into vocal and instrument stems",
    },
  • The @mcp.tool() decorator registers suno_stems_music as an MCP tool with the FastMCP server instance.
    @mcp.tool()
    async def suno_stems_music(
        audio_id: Annotated[
            str,
            Field(description="ID of the audio to separate into stems."),
        ],
        callback_url: Annotated[
            str | None,
            Field(description="Webhook callback URL for asynchronous notifications."),
        ] = None,
    ) -> str:
        """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.
        """
        result = await client.generate_audio(
            action="stems",
            audio_id=audio_id,
            callback_url=callback_url,
        )
        return format_audio_result(result)
  • The generate_audio method on SunoClient that suno_stems_music calls internally. It sends a POST request to /suno/audios with the provided params (including action='stems').
    # Convenience methods for specific endpoints
    async def generate_audio(self, **kwargs: Any) -> dict[str, Any]:
        """Generate audio using the audios endpoint."""
        logger.info(f"🎵 Generating audio with action: {kwargs.get('action', 'generate')}")
        return await self.request("/suno/audios", self._with_async_callback(kwargs))
  • The format_audio_result utility used by suno_stems_music to format the API response as JSON with async submission guidance.
    def format_audio_result(data: dict[str, Any]) -> str:
        """Format audio generation result as JSON.
    
        Args:
            data: API response dictionary
    
        Returns:
            JSON string representation of the result
        """
        return json.dumps(
            _with_submission_guidance(data, "suno_get_task", "suno_get_tasks_batch"),
            ensure_ascii=False,
            indent=2,
        )
Behavior3/5

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

Description mentions returning a Task ID and results with URLs, implying asynchronous behavior, but does not explicitly disclose processing time, required permissions, or whether it modifies original audio. Without annotations, more behavioral context would be beneficial.

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?

Description is concise (6 sentences), front-loaded with purpose, followed by usage guidelines and return info. No unnecessary words.

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 high schema coverage and existence of output schema, description adequately covers core functionality. However, it does not differentiate from sibling suno_all_stems_music or address edge cases like large files.

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 is 3. Description adds minimal value beyond schema by mentioning 'Task ID and stem separation results' but does not elaborate on parameter constraints or formats.

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 individual stems (vocals and instruments), using a specific verb and resource. It differentiates from siblings like suno_all_stems_music by specifying vocals and instrumentals.

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?

The description provides explicit usage scenarios ('Use this when:') for remixing, karaoke, and isolating parts. However, it lacks guidance on when not to use the tool or mention alternatives like suno_all_stems_music.

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