Skip to main content
Glama
Sign In
SunoMCP

SunoMCP

by AceDataCloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

suno_upload_extend

Extend uploaded audio by adding AI-generated sections at a chosen timestamp, using your lyrics and style to continue your own music.

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "audio_id": "<audio_id>",
      "lyric": "<lyric>",
      "continue_at": "<continue_at>"
    },
    "name": "suno_upload_extend"
  }
}

Input Schema

NameRequiredDescriptionDefault
lyricYesLyrics for the extension section.
modelNoModel version to use.chirp-v5-5
styleNoMusic style for the extension.
audio_idYesID of the uploaded audio to extend. Must be an audio uploaded via suno_upload_audio.
continue_atYesPositive continuation boundary in seconds; fractional seconds are preserved.
callback_urlNoWebhook callback URL for asynchronous notifications.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.25
    • changedInput schema / properties / continue_at / description
      Previous value: -"Timestamp in seconds where to start the extension."New value: +"Positive continuation boundary in seconds; fractional seconds are preserved."
    • addedInput schema / properties / continue_at / exclusiveMinimum
      Added value: +0
  2. Changed1 schema field changedv0.1.18
    • changedInput schema / properties / model / enum
      Previous value: -[
-  "chirp-v3-0",
-  "chirp-v3-5",
-  "chirp-v4",
-  "chirp-v4-5",
-  "chirp-v4-5-plus",
-  "chirp-v5",
-  "chirp-v5-5"
-]New value: +[
+  "chirp-v6",
+  "chirp-v6-wild",
+  "chirp-v6-mini",
+  "chirp-v3-0",
+  "chirp-v3-5",
+  "chirp-v4",
+  "chirp-v4-5",
+  "chirp-v4-5-plus",
+  "chirp-v5",
+  "chirp-v5-5"
+]
  3. Addedv0.1.5
  4. Removedv0.1.3
  5. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the key behavioral traits: this is an asynchronous task (returns a Task ID) and it operates only on previously uploaded audio, which prevents misuse on generated tracks. It does not say whether the source audio is preserved or what happens on invalid audio_id, so a small gap remains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose and appropriately short. The two 'Use this when' bullets largely restate the preceding sentences, and the 'Returns' line duplicates the output schema, but neither is enough to hurt readability.

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 an output schema exists and 100% parameter coverage, the description needn't explain return values. It supplies purpose, prerequisite, alternative, and async behavior — enough to call correctly, though side-effect/safety details for this generation operation are thin.

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%, so every parameter (including the model enum, continue_at boundary semantics, and callback_url) is already documented in the schema. The description adds no parameter-level meaning beyond the audio_id prerequisite, which is the baseline-3 case.

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?

States a specific verb and resource — extend an uploaded audio with AI-generated content — and explicitly contrasts it with the sibling suno_extend_music, noting the difference is the source material (uploaded audio vs. generated). An agent can route between the two without opening either schema.

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' conditions plus the hard prerequisite that the audio must have been uploaded via suno_upload_audio, and names the alternative tool it is similar to. This is a textbook when-to-use / which-alternative disclosure.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools