Skip to main content
Glama

suno_extend_music

Add new lyrics and sections to an existing song from a specific timestamp. Continue a generated track with new 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 provided, so description bears full burden. It states the tool returns Task ID and audio info, and maintains style if empty, but lacks details on limitations (e.g., max extension length), side effects, or authentication needs. Adequate but could be more comprehensive.

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?

Delivers core action in the first sentence, then bullet lists usage cases, workflow hint, and return info. No unnecessary words; well organized and front-loaded.

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?

Covers purpose, usage, parameter hints, follow-up step (concat), and return value. Could mention output schema structure or extension length limits, but output schema exists so completeness is strong. Minor gaps prevent a 5.

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 covers all 6 parameters with descriptions. The description adds context about using section markers for lyrics and timestamp format, but does not significantly enhance understanding beyond the schema. Baseline of 3 is appropriate given high coverage.

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?

Clearly states the verb 'extend' and resource 'existing song from a specific timestamp with new lyrics'. Lists specific uses like adding verses, bridge, outro, and distinguishes from sibling tool suno_concat_music by mentioning it for merging segments 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-to-use scenarios (too short, add bridge/outro, build piece by piece) and tells when to use the sibling tool suno_concat_music. The bullet list gives clear context for selection.

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