Skip to main content
Glama
elibarnett

kie-mcp

by elibarnett
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

generate_sounds

Generate loopable sound effects with BPM, key, and loop control via Suno. Downloads to kie/assets/raw/.

Instructions

Generate loopable sound effects with BPM, key, and loop control via Suno. Downloads to kie/assets/raw/.

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
promptYesSound description (e.g. "ambient rain on a tin roof, soft thunder")
filenameNo
soundKeyNoMusical key (e.g. "C", "Am")
soundLoopNoWhether the sound should loop seamlessly
grabLyricsNo
soundTempoNoBPM for the sound
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 (defaults: image 600, video 900, audio 300, speech 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.9/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 disclosure burden. It does reveal one genuine side effect — files are downloaded to kie/assets/raw/ — but says nothing about credit consumption, async/polling behavior, permissions, or what the caller receives, all of which matter for a 12-parameter generation tool.

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 compact sentences with the core capability front-loaded and the output destination trailing. No filler, though the second sentence is a fragment that could be folded into the first.

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?

The rich schema descriptions (wait/async mode, download_dir, estimate_only, max_credits) compensate for much of the terse description, and no output schema exists to explain. Still missing sibling disambiguation and any cost/return expectations, which leaves gaps for a 12-parameter tool with no annotations.

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 coverage is 75%, so the schema already documents most parameters well. The description echoes the key ones ('BPM, key, and loop control' mapping to soundTempo, soundKey, soundLoop) but adds no syntax, ranges, or format guidance beyond the schema.

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 and resource ('Generate loopable sound effects') plus the differentiating attributes (BPM, key, loop control) and the provider (Suno). However, it never distinguishes itself from the close sibling generate_sfx or from generate_music, so an agent cannot tell from the description alone which sound-generation tool to pick.

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 guidance and no mention of alternatives. The sibling list contains generate_sfx and generate_music, whose overlap with this tool is exactly the ambiguity the description should resolve, and it does not.

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