Skip to main content
Glama
elibarnett

kie-mcp

by elibarnett
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

separate_vocals

Separate vocals from instrumentals or split audio into individual stems, then download the results to kie/assets/raw/.

Instructions

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

Input Schema

TableJSON 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
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.
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 / 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"
+]
  2. First observedv4.7.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose that output lands in kie/assets/raw/, which is genuine context, but it omits the long-running/async nature, polling expectations, and whether the source audio is altered. The schema covers wait/poll behavior, but the description adds only the output-location detail.

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 operation. The trailing fragment 'Downloads to kie/assets/raw/.' is terse but useful; overall there is essentially no wasted text.

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 7-parameter, no-annotation, no-output-schema tool, the description is thin: it never explains what the caller receives or references the check_task/download_result polling flow. The schema picks up most of the slack on parameters, but the description leaves behavioral and post-invocation context incomplete.

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 86%, well above the high-coverage threshold, so the schema already documents type, wait, download_dir, and max_wait_seconds thoroughly. The description adds no parameter-level detail beyond restating that files go to the default raw directory, so 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 specific verbs and resources: separating vocals from instrumentals or splitting into individual stems. It's clear what the tool does, but it never differentiates itself from the nearby sibling 'audio_isolation' or 'convert_to_wav', which an agent could easily confuse for the same job.

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 tells you the two modes exist but gives no guidance on when to choose this over adjacent tools like audio_isolation. The mode distinctions it does mention (separate vocal vs split stems) are already spelled out in the type enum description, so no routing value is added.

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