Skip to main content
Glama
elibarnett

kie-mcp

by elibarnett
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

generate_music

Create instrumental or vocal music up to 8 minutes using Suno models via kie.ai, then download the audio file for games, videos, or jingles.

Instructions

Generate music using Suno via kie.ai. Supports V5.5 (custom style), V5 (best quality), V4.5+, V4.5, V4. Up to 8 minutes. Great for game music stems, ambient tracks, and jingles. Polls until done and 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.
modelNoSuno model. V5_5=custom style, V5=best quality. Default: V5V5
styleNoStyle tags (e.g. "Celtic, orchestral, upbeat, fantasy, game music")
titleNoTrack title (optional)
promptYesMusic description (e.g. "upbeat Celtic fantasy adventure, flute and drums, heroic")
filenameNoOutput filename. Auto-generated if omitted.
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.
instrumentalNoNo vocals when true (recommended for game music)
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

A3.6/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 burden, and it does disclose the key behavior: it 'polls until done and downloads to kie/assets/raw/'. However, it omits cost/credit implications, failure behavior, and the blocking-vs-async tradeoff (that detail lives only in the schema's wait param). Useful but incomplete for a paid, long-running generation call.

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?

Short, front-loaded sentences with the core action stated first and useful details following; every clause adds something. Slightly listy but no filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, but the schema is fully documented and the description covers backend, model range, duration, purpose, and the polling/download destination, which is sufficient for an agent to invoke and interpret this tool correctly.

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 100%, so the schema already documents all 9 parameters, setting the baseline at 3. The description adds only duration ('up to 8 minutes') and model tier hints that largely duplicate the model enum descriptions, so it does not meaningfully extend parameter semantics.

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 music using Suno via kie.ai') and adds scope details (model range, up to 8 minutes) plus use cases (game music, ambient, jingles). It clearly separates itself from generative siblings like generate_sfx or generate_tts, though it never names an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Use cases ('great for game music stems, ambient tracks, and jingles') imply when this is appropriate, but there is no explicit routing against siblings such as extend_music, cover_audio, add_vocals, or generate_sfx, and no exclusions or prerequisites are given. Usage is inferable rather than stated.

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