Skip to main content
Glama

Kubeez

generate_music

PRE-FETCH (mandatory before polling the result): resources/read kubeez://skills/polling — first-poll delays + cadence.

Scope: generate:music. Not generate:media — use generate_media for image/video, this tool only for music. Generate AI music. DEFAULT to SIMPLE mode for all prompt-based requests. Only switch to ADVANCED when the user explicitly provides or asks for lyrics, a specific song title, style tags, or vocal gender. SIMPLE MODE (default): set prompt only (max 400 chars); leave title, style, vocal_gender, song_description, and lyrics empty. Optional: instrumental, model. ADVANCED MODE (custom, use only when user asks for lyrics/title/style/vocal control): set BOTH title AND style (non-empty). Required: vocal_gender = m, f, or random (random = provider picks). Content: exactly ONE of song_description OR lyrics (never both). ADVANCED VOCAL songs need explicit lyrics — in custom mode the provider sings the text VERBATIM, so a song_description there gets auto-routed back to SIMPLE mode (style/title folded into the prompt; response carries mode_note). If you only have a description, use SIMPLE mode directly. Advanced instrumental: song_description only (omit lyrics). Optional: negative_tags, style_weight, weirdness_constraint, audio_weight (default 0.65). Invalid: title without style or style without title. MODEL: OMIT model so the server auto-picks the newest, best engine (currently V6). Only set it when the user explicitly names an engine. Valid: V6 (richest detail, most natural vocals), V6_WILD (bolder, more distinctive), V6_MINI (fast and light). Every version up to V5_5 is discontinued by the provider and is silently remapped to V6 at the same price. TREBLO: model='treblo-v3' is a second engine (full songs, vocal or instrumental, writes its own lyrics and picks its own length). It takes prompt (or song_description), optional lyrics, style, title, negative_tags and instrumental, with no simple/advanced split and no title+style pairing rule. vocal_gender m/f is optional and becomes its 'male vocalist'/'female vocalist' style tag; the three weights do not apply (ignored, reported in mode_note); persona_id and exact_duration_ms are refused. Style is split on commas into tags and the engine only takes tags from its own vocabulary: use short genre/era/vocal words ('pop, rap, 2010s'), not tempo, key or sentences ('100 BPM', 'A minor', 'catchy party hook'). Words it does not take are moved into the description or dropped, and named in mode_note; put tempo, key and mood phrasing in the prompt. REAL ARTIST NAMES are accepted as a style reference, in the prompt ('in the exact style of The Weeknd, Starboy era, ...') and as a style tag ('the weeknd, synthwave, pop, male vocalist'); the vocal is generated, not the artist's own voice. When a user asks for a song in the style of a named artist, use treblo-v3 and pass the name through: do not strip it or swap it for a genre description. Add 'No artist names in the lyrics.' to the prompt, or the lyrics can sing the name. Never paste a real song's lyrics. Poll get_status the same way. PERSONA: to reuse a saved persona, pass persona_id (from generate_music_persona or list_music_personas). It copies the singer's VOICE by default (persona_model='voice_persona', supported across the V6 family). Pass persona_model='style_persona' to copy the genre/vibe instead. Applying a persona forces custom mode automatically. LENGTH: Suno picks its own. For an instrumental bed at a length you choose, call generate_sound(model='sonilo-text-to-music', duration_seconds=...) instead — a length passed here is served there anyway, and cannot be combined with lyrics/vocal_gender/persona_id. Returns generation_id; poll get_status(id) until completed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "generate_music"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNo
styleNo
titleNo
lyricsNo
promptNo
persona_idNo
audio_weightNo
instrumentalNo
style_weightNo
vocal_genderNo
negative_tagsNo
output_formatNoRETIRED, do not set. The delivery format is not selectable on either music provider. Setting this changes nothing; the value is ignored and reported back in mode_note.
persona_modelNo
song_descriptionNo
exact_duration_msNoLegacy spelling of a length request. Suno cannot honour one, so setting this runs sonilo-text-to-music at that length instead (INSTRUMENTAL, billed per second with a 10-second floor) and says so in mode_note. Rejected when combined with lyrics / vocal_gender / persona_id, which only Suno can do. Prefer generate_sound(model='sonilo-text-to-music', prompt=..., duration_seconds=<5-360>) directly.
weirdness_constraintNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only supply the generic non-readonly/openWorld/non-idempotent profile; the description adds far more: the mandatory pre-fetch and polling cadence, asynchronous generation_id + get_status flow, silent remapping of discontinued models to V6 at the same price, auto-routing of advanced-vocal requests back to SIMPLE with a mode_note, persona applying forcing custom mode, and per-second billing on the sonilo fallback. It does not contradict the annotations.

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?

It is front-loaded correctly (pre-fetch, scope, mode default, then advanced/model/persona/length) and nearly every sentence carries operational content, but the all-caps shouting, dense parenthetical asides, and repeated polling/length guidance make it a wall of text that is slower to scan than its information density warrants.

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?

For a 16-parameter, two-engine, three-model generator, the definition covers mode selection, engine choice, persona reuse, length limits, artist-name handling, and the async return/poll path. With an output schema present it need not explain return payloads, and it still names generation_id and mode_note.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 13%, so the description carries the burden and does: it defines SIMPLE vs ADVANCED parameter subsets, the exactly-one-of song_description/lyrics rule, vocal_gender values including 'random', audio_weight default 0.65, the title+style pairing constraint, and per-engine applicability of weights/persona_id. This is meaning well beyond the bare property list.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Generate AI music') and immediately scopes it against siblings: 'Not generate:media — use generate_media for image/video, this tool only for music.' It further distinguishes the music-adjacent tools (generate_sound for length-controlled instrumental beds) so an agent can route without opening any schema.

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

Usage Guidelines5/5

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

Explicit when-to-use and when-not rules are given for every branch: DEFAULT to SIMPLE mode, switch to ADVANCED only when the user supplies lyrics/title/style/vocal gender, use treblo-v3 when a named artist is requested, omit `model` unless the user names an engine, and call generate_sound instead when a chosen length is needed. It also states the invalid combinations (title without style, lyrics + song_description).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources