Skip to main content
Glama
elibarnett

kie-mcp

by elibarnett
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

upload_extend_audio

NEW — Extend uploaded audio (NOT a Suno track) with new AI-generated content. For Suno tracks, use extend_music instead.

Instructions

NEW — Extend uploaded audio (NOT a Suno track) with new AI-generated content. For Suno tracks, use extend_music instead.

Input 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
promptNoLYRICS for the extended section (sung as written); omit and set instrumental=true for an instrumental extension.
filenameNo
uploadUrlYesURL of the audio file to extend
continueAtYesREQUIRED in practice: second where the extension starts (> 0 and < the upload's length). kie fails every request without it.
max_creditsNoRefuse to submit if the estimated cost exceeds this many credits (overrides KIE_MAX_CREDITS_PER_CALL). Estimates come from published rates; kie bills the actual amount.
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.
instrumentalNo
estimate_onlyNoReturn the estimated credit cost WITHOUT submitting anything. Use before expensive runs (video, 4K, 1080p upgrades, layer splits).
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.8.0
    • addedInput schema / properties / estimate_only
      Added value: +{
+  "description": "Return the estimated credit cost WITHOUT submitting anything. Use before expensive runs (video, 4K, 1080p upgrades, layer splits).",
+  "type": "boolean"
+}
    • addedInput schema / properties / max_credits
      Added value: +{
+  "description": "Refuse to submit if the estimated cost exceeds this many credits (overrides KIE_MAX_CREDITS_PER_CALL). Estimates come from published rates; kie bills the actual amount.",
+  "type": "number"
+}
  2. Changed4 schema fields changedv5.5.0
    • changedInput schema / properties / continueAt / description
      Previous value: -"Timestamp in seconds where to start the extension"New value: +"REQUIRED in practice: second where the extension starts (> 0 and < the upload's length). kie fails every request without it."
    • 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: -"Description of the extension content"New value: +"LYRICS for the extended section (sung as written); omit and set instrumental=true for an instrumental extension."
    • changedInput schema / required
      Previous value: -[
-  "uploadUrl"
-]New value: +[
+  "uploadUrl",
+  "continueAt"
+]
  3. First observedv4.7.0

TDQS

A4.1/5.0
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, and it does disclose that this is a generative extension of an uploaded asset. However it omits behavioral traits an agent would want — that it submits a credit-billing generation, the async/polling option, and long-run timeouts — though much of that is covered in the schema. Given zero annotation coverage and a two-sentence description, 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?

Two sentences, zero waste, and the routing distinction is front-loaded in the first clause. The 'NEW —' marker is a minor framing tag rather than filler.

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 a 13-parameter generation tool with no annotations and no output schema, the description is very thin — it covers only the routing distinction and says nothing about async behavior, credit accounting, or return handling. The rich per-parameter schema descriptions do much of the heavy lifting, which keeps this at minimum-viable rather than inadequate.

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 69%, and the description adds no parameter-level meaning whatsoever. With majority-but-not-full schema coverage, the baseline of 3 applies; the description does nothing to compensate for the remaining undocumented parameters.

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 names a specific verb and resource ('Extend uploaded audio with new AI-generated content') and, critically, states the scope boundary ('NOT a Suno track'). It distinguishes itself from sibling extend_music without the reader needing to open 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?

It gives an explicit routing rule: use this tool for uploaded audio, use extend_music for Suno tracks. The alternative sibling is named and the condition that selects it is stated, leaving nothing 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