Skip to main content
Glama
Sign In
kie-mcp

kie-mcp

by elibarnett
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

add_vocals

Add AI vocals to uploaded instrumental audio via Suno.

Instructions

Add AI vocals to uploaded instrumental audio via Suno.

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
styleNo
titleNo
promptYesLyrics or vocal description
filenameNo
uploadUrlYesURL of instrumental audio
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.
negativeTagsNo
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. Changed1 schema field 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"
+]
  3. First observedv4.7.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and one sentence does not cover it. It never mentions credit consumption, that this is a long-running generation with an async option, or any prerequisite on the uploaded audio; the schema's wait/max_credits/estimate_only fields partially fill the gap but the description adds almost nothing.

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?

A single front-loaded sentence with zero wasted words. It is tight and readable, though for a 12-parameter generation tool it is arguably undersized rather than optimally scoped.

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

Completeness2/5

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

With 12 parameters, no annotations, and no output schema, an agent needs more: the uploadUrl prerequisite, the credit/cost model, and the async submit-then-poll workflow are all omitted. The description is not sufficient on its own to call this tool correctly without reading the whole schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 58%, below the 80% baseline, so the description should compensate for undocumented parameters — and it does not. Key fields like model (9-value enum), style, title, filename, and negativeTags have no description text anywhere, and the description mentions no parameter semantics at all.

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?

The description states a specific verb and resource ('Add AI vocals to uploaded instrumental audio') and names the provider (Suno), so the agent knows exactly what the tool produces. It does not explicitly contrast itself with close siblings such as add_instrumental (the inverse operation) or extend_music, but the operation is unambiguous.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no alternatives are named. The agent must infer that uploadUrl must come from a prior upload (e.g. upload_file) and that check_task/download_result are the polling path — none of that routing is stated.

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