Skip to main content
Glama

var2_create_audio

Create, COVER, EXTEND, or edit MUSIC / a song / a track (Suno). type ∈ create-music (default) | cover-music | extend-music | replace-music-section. "Cover this song in a " / "redo my track as jazz" / "same melody, new style / new lyrics" → type=cover-music with the song in audio_url (an https URL — upload a local file with var2_upload_asset first) OR audioRecordId (a var2 track); style = the new style; lyrics optional (empty keeps the original words); instrumental=true drops vocals. Source ≤ 8 minutes; returns 2 takes. Copyrighted recordings are NOT allowed as the source: Suno fingerprints it and rejects commercial songs ("matches an existing recording"). Only the user's own or royalty-free songs, e.g. a var2 track. "extend that track by N seconds" / "make the song longer" / "continue past 1:00" → type=extend-music, track id in audioRecordId. "That track" without a re-pasted id = the track from earlier in this conversation — use its placeholder_id from context; never answer null / ask for a link. "replace / swap seconds X-Y of the track" → type=replace-music-section. ANY make/extend/lengthen/replace-section on a song / track / music = THIS tool — never a video or image tool, never an invented tool. "A song AND cover art" → START HERE (art = follow-up var2_create_image, not an upload). customMode=false: prompt = song description ≤2800 chars on V6/V6_WILD (≤500 on V5_5 and older). customMode=true: prompt = full lyrics; style + title required. Never name real artists or songs (copyright filter).

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": "var2_create_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoDefault create-music. cover-music = re-style an existing song (audio_url or audioRecordId), keeping its melody.
modelNoDefault suno.
styleNoRequired when customMode=true. Max 200 chars.
titleNoRequired when customMode=true.
lyricsNocover-music only: new lyrics for the same melody. Omit to keep the original words.
promptNocustomMode=false: song description ≤2800 chars on V6/V6_WILD, ≤500 on older (Suno writes lyrics). customMode=true: full lyrics.
audio_urlNocover-music only: https URL of the song to cover (≤ 8 min). Any public URL, a var2 storage URL, or the url from var2_upload_asset / var2_request_upload for a local file.
continueAtNoRequired for extend-music. Seconds offset to extend from.
customModeNoDefault false. Set true when the user provides exact lyrics. Requires style + title.
infillEndSNoRequired for replace-music-section. Window end in seconds (> infillStartS; ~6-60s window).
webhook_urlNoOptional. https:// URL var2 POSTs a signed delivery to when the asset is ready (or fails). Signature header: X-VAR2-Signature: t=<unix>, v1=<hex(hmac_sha256(webhook_secret, t + "." + body))>. Retried with exponential backoff (8 attempts over ~4 days).
audio_weightNocover-music only: closeness to the source sound (0–1). Omit to let Suno decide.
infillStartSNoRequired for replace-music-section. Window start in seconds.
instrumentalNo
vocal_genderNocover-music only: preferred vocal gender.
audioRecordIdNoRequired for extend-music / replace-music-section; one of audio_url / audioRecordId for cover-music. placeholder_id from the source var2_create_audio call (var2-hosted tracks only). "That track" = the most recent track in this conversation — take its placeholder_id from context rather than declining.
model_versionNoDefault V6 (latest). V6_WILD for bolder, more experimental takes. Older only for a specific sound.V6

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedInput schema / properties / audioRecordId / description
      Previous value: -"Required for extend-music / replace-music-section. placeholder_id from the source var2_create_audio call (var2-hosted tracks only). \"That track\" = the most recent track in this conversation — take its placeholder_id from context rather than declining."New value: +"Required for extend-music / replace-music-section; one of audio_url / audioRecordId for cover-music. placeholder_id from the source var2_create_audio call (var2-hosted tracks only). \"That track\" = the most recent track in this conversation — take its placeholder_id from context rather than declining."
    • addedInput schema / properties / audio_url
      Added value: +{
      +  "description": "cover-music only: https URL of the song to cover (≤ 8 min). Any public URL, a var2 storage URL, or the url from var2_upload_asset / var2_request_upload for a local file.",
      +  "type": "string"
      +}
    • addedInput schema / properties / audio_weight
      Added value: +{
      +  "description": "cover-music only: closeness to the source sound (0–1). Omit to let Suno decide.",
      +  "maximum": 1,
      +  "minimum": 0,
      +  "type": "number"
      +}
    • addedInput schema / properties / lyrics
      Added value: +{
      +  "description": "cover-music only: new lyrics for the same melody. Omit to keep the original words.",
      +  "maxLength": 5000,
      +  "type": "string"
      +}
    • changedInput schema / properties / type / description
      Previous value: -"Default create-music."New value: +"Default create-music. cover-music = re-style an existing song (audio_url or audioRecordId), keeping its melody."
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "create-music",
      -  "extend-music",
      -  "replace-music-section"
      -]New value: +[
      +  "create-music",
      +  "cover-music",
      +  "extend-music",
      +  "replace-music-section"
      +]
    • addedInput schema / properties / vocal_gender
      Added value: +{
      +  "description": "cover-music only: preferred vocal gender.",
      +  "enum": [
      +    "m",
      +    "f"
      +  ],
      +  "type": "string"
      +}
  2. Changed4 schema fields changed
    • changedInput schema / properties / model_version / default
      Previous value: -"V5_5"New value: +"V6"
    • changedInput schema / properties / model_version / description
      Previous value: -"Default V5_5 (latest). Older only for a specific sound."New value: +"Default V6 (latest). V6_WILD for bolder, more experimental takes. Older only for a specific sound."
    • changedInput schema / properties / model_version / enum
      Previous value: -[
      -  "V4",
      -  "V4_5",
      -  "V4_5PLUS",
      -  "V4_5ALL",
      -  "V5",
      -  "V5_5"
      -]New value: +[
      +  "V4",
      +  "V4_5",
      +  "V4_5PLUS",
      +  "V4_5ALL",
      +  "V5",
      +  "V5_5",
      +  "V6",
      +  "V6_WILD"
      +]
    • changedInput schema / properties / prompt / description
      Previous value: -"customMode=false: song description ≤500 chars (Suno writes lyrics). customMode=true: full lyrics."New value: +"customMode=false: song description ≤2800 chars on V6/V6_WILD, ≤500 on older (Suno writes lyrics). customMode=true: full lyrics."
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations carry only a title, so the description bears the load and does well: it discloses the 8-minute source cap, that 2 takes are returned, that Suno fingerprints and rejects copyrighted recordings, and that real artist/song names trip a copyright filter. It omits the async lifecycle (that results come back via var2_get_audio_result / webhook) and cost implications, keeping it just short of a 5.

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?

Front-loaded with mode routing followed by per-mode usage, prerequisites and constraints — a sensible order. It is dense and somewhat repetitive (the all-caps 'ANY make/extend/lengthen/replace-section ... = THIS tool' and the 'that track' instruction appear twice in spirit), but nearly every sentence carries operational value.

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

Completeness4/5

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

For a 17-parameter generation tool with no output schema, the description covers prerequisites (upload flow), mode selection, content limits and result count, which is substantial. The missing piece is the retrieval path — it never says the call is asynchronous or that output must be fetched via var2_get_audio_result/webhook — though webhook_url's schema text partially compensates.

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

Parameters4/5

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

Schema coverage is 94%, so the baseline is 3; the description nevertheless adds genuine meaning — prompt char limits differing by model version, customMode=true meaning 'prompt = full lyrics' with style+title required, empty lyrics keeping original words, and the audio_url vs audioRecordId choice per mode. It doesn't add much for continueAt/infillStartS/infillEndS beyond the schema, but the gaps are minor.

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?

Opens with a specific verb+resource (create/cover/extend/edit music via Suno) and enumerates the four concrete modes in the `type` enum. It explicitly contrasts itself with siblings ('never a video or image tool', art = follow-up `var2_create_image`), so an agent can distinguish it from var2_create_video / var2_create_image without opening schemas.

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?

Gives explicit user-utterance triggers mapped to each mode ('Cover this song in a <style>' → cover-music, 'extend that track by N seconds' → extend-music, 'replace seconds X-Y' → replace-music-section). It also names the alternative path for local files (var2_upload_asset first) and instructs that 'A song AND cover art' starts here — clear when/when-not routing.

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