Skip to main content
Glama

suno_upload_extend

Extend your uploaded audio by adding AI-generated sections with custom lyrics, style, and timing. Ideal for continuing your own music recordings with new content.

Instructions

Extend an uploaded audio (your own music) with new AI-generated content.

Similar to suno_extend_music but works with audio you uploaded via
suno_upload_audio. Allows you to add new sections to your own music.

Use this when:
- You uploaded your own music and want to extend it
- You want to add AI-generated sections to your existing recordings

Returns:
    Task ID and the extended audio information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
audio_idYesID of the uploaded audio to extend. Must be an audio uploaded via suno_upload_audio.
lyricYesLyrics for the extension section.
continue_atYesTimestamp in seconds where to start the extension.
styleNoMusic style for the extension.
modelNoModel version to use.chirp-v5-5
callback_urlNoWebhook callback URL for asynchronous notifications.

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 carries full burden. States return values but does not disclose whether extension modifies original audio or creates new, nor any permissions or limitations. Adequate but not 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?

Concise, front-loaded with key action, then comparison, then bullet list for usage, then return info. No redundant sentences.

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, and return values. With 6 parameters and no annotations, could include more about constraints (e.g., audio length, supported formats), but still provides sufficient context for an AI agent.

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 coverage is 100%, so baseline 3. Description adds no extra parameter context beyond schema; however, schema descriptions are self-explanatory.

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 function: extend uploaded audio with AI content. Differentiates from sibling suno_extend_music by specifying it works with audio uploaded via suno_upload_audio.

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?

Explicitly lists two scenarios for use, and draws comparison to a sibling tool, providing clear context for when to choose this tool.

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