Skip to main content
Glama
elibarnett

kie-mcp

by elibarnett
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

add_vocals

Generate AI vocals for uploaded instrumental audio by providing lyrics or a vocal description. Suno adds singing to your track.

Instructions

Add AI vocals to uploaded instrumental audio via Suno.

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

TDQS

C2.6/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 it says nothing about blocking vs async execution, expected generation latency, credit consumption, or what files are produced. The only hints (wait, max_wait_seconds) live in the schema, not the description, and the far more complex async/polling workflow is never surfaced.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with no filler is front-loaded and easy to scan, but it is under-specified rather than concise — the brevity comes at the cost of any operational context.

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?

For a 10-parameter generation tool with an async polling mode, no annotations, and no output schema, a one-line description is not sufficient. An agent cannot infer the polling contract, output artifacts, or how the vocal models differ from what the schema alone provides.

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 only 50%, leaving model, style, title, filename, and negativeTags undocumented in both places. The description adds zero parameter meaning (no lyric/format hints for prompt, no model-selection advice), so it fails to compensate for the coverage gap.

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+resource combination ('Add AI vocals to uploaded instrumental audio') and names the underlying provider (Suno), which makes it distinguishable from the reverse-direction sibling add_instrumental. It does not explicitly name or route against alternatives, but the purpose 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?

The phrase 'uploaded instrumental audio' weakly implies a prerequisite that an instrumental already exists at a URL, but there is no explicit when-to-use guidance, no mention of when to prefer add_instrumental/cover_audio/generate_music, and no note on credit cost or eligibility.

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