Skip to main content
Glama
elibarnett

kie-mcp

by elibarnett
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

create_music_video

Generate an MP4 music video visualization from a Suno track. Downloads to kie/assets/raw/.

Instructions

Generate an MP4 music video visualization from a Suno track. 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.
authorNoAuthor name for video credits
taskIdYesTask ID of the Suno generation
audioIdYesAudio ID from sunoData
filenameNo
domainNameNoDomain name for video branding
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 (default: audio 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. 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 disclosure burden. It reveals a side effect (writes an MP4 into kie/assets/raw/), but says nothing about cost/credits, the fact that blocking is the default (wait=true), or async behavior — all of which live only in the schema, leaving a real gap for a paid generative 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 short sentences, front-loaded with the action and output artifact, no filler. The second sentence is a fragment, but it earns its place by naming the download destination.

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 costly generative tool with 10 parameters, no output schema, and no annotations, the description is thin. The rich schema compensates on parameters, but credit behavior, blocking-vs-async default, and what the returned MP4 contains are left unaddressed.

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 90%, so the schema already documents taskId, audioId, wait, estimate_only, max_credits, max_wait_seconds and download_dir in detail. The description adds no parameter-level meaning beyond pointing at the Suno source, so baseline 3 is correct.

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, output format, and source: 'Generate an MP4 music video visualization from a Suno track.' This tells an agent it produces video from an existing Suno track, distinguishing it from generate_music (audio) and generate_video (generic video). It stops short of naming the sibling it most resembles (generate_video) to make the split 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 description implies a prerequisite (a Suno track must exist) but gives no explicit when-to-use or when-not-to-use guidance, and never contrasts itself with generate_video. An agent gets no routing rule for choosing this over other video tools.

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