Skip to main content
Glama

suno_concat_music

Merge extended song segments into a single continuous audio file. Combine multiple music extensions into one complete composition.

Instructions

Concatenate extended song segments into a single complete audio file.

After extending a song multiple times with suno_extend_music, use this tool
to merge all the segments into one continuous audio file.

Use this when:
- You've extended a song one or more times
- You want a single audio file instead of multiple segments
- You're ready to finalize a long-form composition

Returns:
    Task ID and the concatenated audio information with the full song.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
audio_idYesID of the LAST segment of an extended song chain. Suno will automatically find and merge all connected segments.
callback_urlNoWebhook callback URL for asynchronous notifications. When provided, the API will call this URL when the concatenation is complete.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function that concatenates extended song segments into a single audio file. It takes an audio_id (the last segment of an extended song chain) and optional callback_url, then calls the Suno API with action='concat' to merge all connected segments.
    @mcp.tool()
    async def suno_concat_music(
        audio_id: Annotated[
            str,
            Field(
                description="ID of the LAST segment of an extended song chain. Suno will automatically find and merge all connected segments."
            ),
        ],
        callback_url: Annotated[
            str | None,
            Field(
                description="Webhook callback URL for asynchronous notifications. When provided, the API will call this URL when the concatenation is complete."
            ),
        ] = None,
    ) -> str:
        """Concatenate extended song segments into a single complete audio file.
    
        After extending a song multiple times with suno_extend_music, use this tool
        to merge all the segments into one continuous audio file.
    
        Use this when:
        - You've extended a song one or more times
        - You want a single audio file instead of multiple segments
        - You're ready to finalize a long-form composition
    
        Returns:
            Task ID and the concatenated audio information with the full song.
        """
        result = await client.generate_audio(
            action="concat",
            audio_id=audio_id,
            callback_url=callback_url,
        )
        return format_audio_result(result)
  • The @mcp.tool() decorator registers the suno_concat_music function as an MCP tool, making it available to the MCP server.
    @mcp.tool()
  • Type definition for SunoModel, a Literal type defining valid Suno model versions. Used as a type annotation in the suno_concat_music tool signature (indirectly via imports in other tools).
    SunoModel = Literal[
        "chirp-v3-0",
        "chirp-v3-5",
        "chirp-v4",
        "chirp-v4-5",
        "chirp-v4-5-plus",
        "chirp-v5",
        "chirp-v5-5",
    ]
  • Helper function that formats the audio generation result as a JSON string. It processes the API response dictionary and adds submission guidance for checking task status. Called by suno_concat_music to format its return value.
    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,
        )
  • main.py:187-189 (registration)
    Documentation entry listing suno_concat_music in the available tools list with its description for display purposes.
        "name": "suno_concat_music",
        "description": "Merge extended segments into complete audio",
    },
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses the core behavioral trait (merging segments into one continuous file) and the finalization nature of the operation ('ready to finalize'). It mentions the return includes a Task ID, hinting at asynchronous processing, though it could clarify whether original segments remain accessible post-concatenation.

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?

Front-loaded with the core action in the first sentence. Uses a structured 'Use this when:' list for preconditions and a 'Returns:' section for output. No filler text; every sentence provides distinct information about purpose, prerequisites, or output.

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 2-parameter workflow tool with 100% schema coverage and an existing output schema, the description is complete. It explains the relationship to sibling tools, the workflow context, and mentions the return value (Task ID and audio info) without needing to duplicate full output schema details.

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 baseline is 3. The main description adds workflow context ('After extending... use this') that supports understanding the audio_id parameter, but does not add specific syntax, format details, or semantics beyond what the schema already provides for callback_url or audio_id.

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 opens with a specific verb ('Concatenate') and resource ('song segments'), clearly stating it creates a 'single complete audio file.' It distinguishes itself from suno_extend_music by specifying this merges existing segments rather than creating new extensions.

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?

Provides explicit 'Use this when:' bullet points listing three clear conditions (post-extension, desire for single file, finalization readiness). Explicitly names the prerequisite sibling tool suno_extend_music, establishing the workflow sequence.

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/MCPSuno'

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