Skip to main content
Glama
elibarnett

kie-mcp

by elibarnett
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

extend_music

Extend or continue an existing Suno track from a chosen timestamp. Provide the audioId from a previous generate_music task and the lyrics prompt for the new section.

Instructions

Extend/continue an existing Suno track from a specific point. Requires audioId from a previous generate_music task.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
waitNoSet false to submit and return immediately with the task_id (async mode) — then poll with check_task and fetch with download_result. Recommended for long generations to avoid client-side watchdog timeouts.
modelNoV5
styleNoStyle tags for the extension
titleNo
promptYesLYRICS for the extended section (Suno sings this text). Give real lyric lines; a short instruction like "add an outro" is rejected as malformed lyrics (error 531, refunded).
audioIdYesAudio ID from a previous Suno generation (from sunoData)
filenameNo
continueAtNoTimestamp in seconds to continue from
download_dirNoAbsolute directory to save the file(s) into (created if missing). Defaults to the server's kie/assets/raw/. Must be absolute — the MCP server's working directory is not the caller's.
defaultParamFlagNoUse default params from original track
max_wait_secondsNoOverride the blocking-mode polling budget in seconds (default: audio 300). Ignored when wait=false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv5.5.0
    • changedInput schema / properties / model / enum
      Previous value: -[
-  "V3_5",
-  "V4",
-  "V4_5",
-  "V4_5PLUS",
-  "V4_5ALL",
-  "V5",
-  "V5_5"
-]New value: +[
+  "V4",
+  "V4_5",
+  "V4_5PLUS",
+  "V4_5ALL",
+  "V5",
+  "V5_5",
+  "V6",
+  "V6_MINI",
+  "V6_WILD"
+]
    • changedInput schema / properties / prompt / description
      Previous value: -"Prompt for the extension"New value: +"LYRICS for the extended section (Suno sings this text). Give real lyric lines; a short instruction like \"add an outro\" is rejected as malformed lyrics (error 531, refunded)."
  2. First observedv4.7.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, yet it only states the audioId prerequisite. It says nothing about cost/credit consumption, async vs blocking execution, refund behavior on malformed input, or mutation scope — behavior that matters for a paid, stateful generation call.

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?

Two tight sentences with the core action front-loaded and the prerequisite second. Nothing is wasted, though the minimal content reflects under-specification rather than meaningful economy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter generator tool with no output schema and no annotations, the description is thin, omitting async/cost/refund context. The relatively rich per-parameter schema descriptions partially compensate, keeping this at the minimum-viable level rather than a gap.

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 73%, so most parameters are already documented in the schema (wait, prompt, download_dir, max_wait_seconds). The description adds only the audioId requirement, which the schema already conveys, so it does not meaningfully extend parameter semantics. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (extend/continue) and resource (an existing Suno track) plus scoping detail (from a specific point). An agent can distinguish it from generate_music, but the description does not differentiate it from close siblings like replace_section or upload_extend_audio.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Provides one prerequisite (audioId from a previous generate_music task), which implies when the tool is usable. It gives no explicit rule for choosing between this and replace_section, upload_extend_audio, or add_instrumental, leaving alternatives to inference.

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