Skip to main content
Glama

suno_concat_music

Merge extended song segments into one continuous audio file. Provide the last segment's ID to combine all connected parts into a complete track.

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
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that it merges all connected segments automatically and returns Task ID + audio info. It does not mention side effects, authentication needs, or error handling, which are minor gaps.

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?

The description is concise with a clear front-loaded purpose, followed by usage guidelines and return value. Every sentence adds value without repetition.

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?

The description covers the main purpose, usage scenarios, and return value. It does not mention prerequisites (e.g., must have extended segments) or error conditions, but given the simplicity of the tool and existence of an output schema, it is nearly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and the description adds critical context beyond the schema: for audio_id, it clarifies to use the 'LAST segment' and that Suno will automatically find all connected segments. For callback_url, it explains the webhook purpose.

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's verb 'Concatenate extended song segments' and identifies the resource as 'extended song segments'. It distinguishes from sibling tools like suno_extend_music by specifying the purpose of merging after multiple extensions.

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?

Explicitly lists when to use: after extending a song multiple times, wanting a single file, or finalizing a composition. However, does not mention when not to use or alternatives, leaving some ambiguity.

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