Skip to main content
Glama
hedging8563

TokenLab MCP Server

by hedging8563
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Create music generation task

create_music

Generate music tracks with Suno by submitting a prompt; returns a task ID to poll for completion.

Instructions

Creates a music generation task using Suno. Returns a task ID for polling.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mvNoOfficial Suno model version. Required when creating music (action omitted or MUSIC); omit for lyric…
tagsNo
modelNosuno_music
titleNo
actionNo
promptNoMusic description. Required for music, lyrics, upload-cover, and upload-extend requests; omit for a…
audio_urlNoPublicly reachable reference or uploaded audio URL. Defaults to upload-cover when audio_operation i…
continue_atNoTimestamp in seconds for continuation flows. Required when audio_operation is upload-extend.
negative_tagsNoStyles to avoid. Required when audio_operation is add-instrumental.
audio_operationNoUploaded-audio mode. upload-extend requires continue_at; add-instrumental requires audio_url, title…
continue_clip_idNoClip ID to continue when extending an existing generation.
make_instrumentalNoGenerate instrumental output without vocals.
X-TokenLab-Delivery-PolicyNoPer-request Delivery policy. Overrides the API key and Workspace defaults. Auto tries TokenLab Veri…

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.6.24
    • addedInput schema / properties / X-TokenLab-Delivery-Policy
      Added value: +{
+  "description": "Per-request Delivery policy. Overrides the API key and Workspace defaults. Auto tries TokenLab Veri…",
+  "enum": [
+    "auto",
+    "verified",
+    "official"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / audio_operation / description
      Previous value: -"Uploaded-audio mode. upload-extend requires continue_at; add-instrumental requires audio_url, title, tags, and negative_tags."New value: +"Uploaded-audio mode. upload-extend requires continue_at; add-instrumental requires audio_url, title…"
    • changedInput schema / properties / audio_url / description
      Previous value: -"Publicly reachable reference or uploaded audio URL. Defaults to upload-cover when audio_operation is omitted."New value: +"Publicly reachable reference or uploaded audio URL. Defaults to upload-cover when audio_operation i…"
    • changedInput schema / properties / mv / description
      Previous value: -"Official Suno model version. Required when creating music (action omitted or MUSIC); omit for lyrics-only requests."New value: +"Official Suno model version. Required when creating music (action omitted or MUSIC); omit for lyric…"
    • changedInput schema / properties / prompt / description
      Previous value: -"Music description. Required for music, lyrics, upload-cover, and upload-extend requests; omit for add-instrumental."New value: +"Music description. Required for music, lyrics, upload-cover, and upload-extend requests; omit for a…"
  2. Changed1 schema field changedv0.6.4
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  3. Addedv0.3.1

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the mutation profile is covered. The description adds genuinely useful async context ('Returns a task ID for polling'), but says nothing about cost/credit consumption, latency, or what happens with the delivery-policy header — modest added value over 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.

Conciseness4/5

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

Two tight sentences with the core purpose and the async return front-loaded; nothing is padded or repetitive. It is arguably under-sized for a 13-parameter multi-mode tool, but there is no wasted language.

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

Completeness2/5

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

With no output schema and 13 parameters supporting at least four distinct flows (music, lyrics, cover/extend, instrumental), the description leaves the agent without the mode selection logic, the conditional requirements, or the polling follow-up step. For this complexity level it is materially incomplete.

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

Parameters2/5

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

Schema description coverage is a middling 69% across 13 parameters, and the description contributes zero parameter meaning — no explanation of mv, tags, prompt, title, or the conditional requirements among action/audio_operation/continue_at. With conditional-required params present and coverage below 80%, the description should be compensating and does not.

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 ('Creates a music generation task using Suno') and names the async return ('task ID for polling'), which cleanly separates it from create_speech, create_video and create_image. However, the tool actually spans lyric generation and three uploaded-audio operations per the schema, and the description's narrower 'music generation' framing understates that scope.

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?

No when-to-use guidance, no mention of the MUSIC vs LYRICS action switch, no explanation of when the audio_operation modes (upload-cover/extend/add-instrumental) apply, and no pointer to the sibling poll tool (get_task_status) despite promising a task ID. The agent gets no routing help at all.

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