Skip to main content
Glama
elibarnett

kie-mcp

by elibarnett
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

separate_vocals

Separate vocals from instrumentals, or split into individual stems. Downloads to kie/assets/raw/.

Instructions

Separate vocals from instrumentals, or split into individual stems. Downloads to kie/assets/raw/.

Input Schema

NameRequiredDescriptionDefault
typeNosplit_stem_advanced = NEW finer multi-stem split (market API). separate_vocal=vocals+instrumental, split_stem=individual instrumentsseparate_vocal
waitNoSet false to submit and return immediately with the task_id (async mode) — then poll with check_task and fetch with download_result.
taskIdYesTask ID of the Suno generation
audioIdYesAudio ID from sunoData
filenameNo
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.
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. Changed2 schema fields changedv5.5.0
    • changedInput schema / properties / type / description
      Previous value: -"separate_vocal=vocals+instrumental, split_stem=individual instruments"New value: +"split_stem_advanced = NEW finer multi-stem split (market API). separate_vocal=vocals+instrumental, split_stem=individual instruments"
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "separate_vocal",
-  "split_stem"
-]New value: +[
+  "separate_vocal",
+  "split_stem",
+  "split_stem_advanced"
+]
  3. First observedv4.7.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the default download destination (kie/assets/raw/), which is useful, but it omits that this submits a credit-consuming paid job, that it blocks by default, and that async submission/polling is possible — all behaviors an agent needs to avoid surprises.

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 short sentences, front-loaded with the core action and ending with the download side effect. Nothing is padded, though the extreme brevity leaves gaps it could have filled cheaply.

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 9-parameter paid generation tool with no annotations and no output schema, the description is thin: it does not mention the required taskId/audioId inputs, credit consumption, or the async submit-then-poll workflow. The rich inline schema descriptions compensate substantially, but the top-level description is only minimally complete.

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 89%, so the schema already documents nearly every parameter, including the type enum's three modes, wait/async behavior, and credit guardrails. The description adds no syntax or format detail beyond what the schema provides, so the baseline 3 applies.

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?

Names a specific verb (separate/split) and resource (vocals, instrumentals, individual stems), so the agent immediately knows the operation. However it never distinguishes itself from the close sibling audio_isolation, which plausibly overlaps.

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?

The description says what it does but gives no when-to-use guidance, no prerequisites (it needs an existing Suno taskId/audioId), and no routing versus siblings such as audio_isolation or add_vocals/add_instrumental. The 'or split into individual stems' phrasing hints at the type enum but does not explain when each mode is appropriate.

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