Skip to main content
Glama

suno_extend_music

Extend existing songs from specific timestamps by adding new lyrics to build longer tracks with additional verses, bridges, or outros.

Instructions

Extend an existing song from a specific timestamp with new lyrics.

This allows you to continue a previously generated song, adding new sections
like additional verses, a bridge, or an outro.

Use this when:
- A generated song is too short and you want to add more
- You want to add a bridge or outro to an existing song
- You're building a longer song piece by piece

After extending multiple times, use suno_concat_music to merge all segments.

Returns:
    Task ID and the extended audio information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
audio_idYesID of the audio to extend. This is the 'id' field from a previous generation result.
lyricYesLyrics for the extended section. Use section markers like [Verse], [Chorus], [Bridge], [Outro]. The extension will continue from where the original song left off.
continue_atYesTimestamp in seconds where to start the extension. For example, 120.5 means continue from 2 minutes and 0.5 seconds into the song.
styleNoMusic style for the extension. Leave empty to maintain the original style, or specify to change the style mid-song.
modelNoModel version to use for the extension.chirp-v5-5
callback_urlNoWebhook callback URL for asynchronous notifications. When provided, the API will call this URL when the extension is complete.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
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 async nature (Task ID return), the multi-step workflow requiring concatenation, and the webhook callback option. It could improve by clarifying whether the original audio is modified or if new segments are created.

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?

Excellent structure with front-loaded purpose statement, followed by elaboration, bulleted usage scenarios, workflow guidance, and return value documentation. No redundant or wasted sentences.

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 tool with 6 parameters (100% schema coverage) and an output schema, the description is complete. It covers purpose, usage contexts, sibling relationships, and return values without needing to replicate 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%, establishing a baseline of 3. The description provides high-level context mapping to parameters (timestamp, lyrics) but does not add semantic details, syntax guidance, or examples beyond what the schema already provides.

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 core action ('Extend an existing song from a specific timestamp with new lyrics') and distinguishes this tool from siblings by explaining it creates segments that later require suno_concat_music to merge.

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:' scenarios (song too short, adding bridge/outro, building piece by piece) and explicitly names the sibling tool suno_concat_music as the required next step for merging multiple extensions.

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