Skip to main content
Glama

suno_extend_music

Add new lyrics to an existing song from a specific timestamp to create longer compositions 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
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 mentions return value (Task ID and extended audio) and implies async behavior via callback_url, but does not disclose whether the operation is destructive (e.g., overwrites original) or requires specific permissions. This is adequate but not rich.

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 and well-structured with bullet points for usage scenarios and a clear 'Returns' section. Every sentence adds value, and front-loading clearly states the core action.

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 6 parameters (3 required) and an output schema, the description adequately explains the workflow. It mentions the callback_url for async, and the return summary suffices. Minor gap: no mention of whether extension is synchronous or asynchronous, but the callback_url hint covers it.

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

Parameters4/5

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

Schema description coverage is 100%, so baseline is 3. The description adds value by providing examples for the 'lyric' parameter (section markers like [Verse]) and a timestamp example for 'continue_at.' This extra context justifies a score above baseline.

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 purpose: 'Extend an existing song from a specific timestamp with new lyrics.' It uses a specific verb (extend), identifies the resource (existing song), and distinguishes from sibling tools like suno_concat_music (merging) and suno_generate_music (generating new).

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?

Explicit usage scenarios are listed: when a song is too short, to add a bridge/outro, or building a song piece by piece. It also directs to use suno_concat_music after multiple extensions, providing clear when-to-use and alternatives.

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