Skip to main content
Glama
elibarnett

kie-mcp

by elibarnett
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

generate_sounds

Create loopable sound effects with custom BPM, key, and loop controls via Suno, then download them to kie/assets/raw/.

Instructions

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

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
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
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 (defaults: image 600, video 900, audio 300, speech 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

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It adds one genuine behavioral fact — results are downloaded to kie/assets/raw/ — but that destination is already stated in the download_dir schema description, so the marginal value is small. It does not disclose the blocking/async behavior, cost, or failure handling that a generation tool should surface.

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

Conciseness5/5

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

Two short sentences, front-loaded with the action and resource, followed by the output location. No filler or redundancy; every clause carries information.

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 10-parameter tool with no annotations and no output schema, the description is only marginally sufficient. It covers purpose, three parameters, and the save destination, but omits sibling differentiation, model-selection guidance, and any behavioral context an agent would want before invoking a long-running generated-audio call.

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 70%, above the midpoint, so the schema already documents prompt, soundKey, soundLoop, soundTempo, wait, download_dir, and max_wait_seconds. The description's mention of BPM, key, and loop control echoes those fields without adding syntax or constraints. Params like model, filename, and grabLyrics remain undocumented in both places, but the baseline 3 is appropriate given the schema does most of the work.

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 provider (Suno) and three controllable dimensions (BPM, key, loop). This is more than a restatement of the name. However, it does not distinguish itself from the very similar sibling generate_sfx (and generate_music), so an agent cannot tell which to pick from the description alone.

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. With generate_sfx and generate_music in the sibling set, the agent gets no signal about when this loop-oriented sound tool is preferred over those alternatives. Usage must be inferred entirely from the name.

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