Skip to main content
Glama

cover_audio

Generate a cover version of an existing audio track using Suno models. Submit an upload URL and choose vocal mode to create a task that returns status and output URLs.

Instructions

Create a Suno task on RunAPI (cover audio). Returns a task id, status, and output URLs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
waitNoPoll until the task reaches a terminal status.
modelNoRunAPI model slug for this model line.
styleNoMusic style.
titleNoMusic title.
lyricsNoExact cover lyrics to sing.
promptNoCover brief for automatic lyrics.
persona_idNoPersona ID.
timeout_msNo
upload_urlYesURL of the audio file to cover.
vocal_modeYesVocal generation mode.
audio_weightNoAudio weight (0-1).
callback_urlNoWebhook URL for async notifications.
persona_typeNoPersona type.
style_weightNoStyle adherence weight (0-1).
vocal_genderNoVocal gender.
negative_tagsNoStyles to avoid.
poll_interval_msNo
weirdness_constraintNoWeirdness constraint (0-1).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.6
    • changedInput schema / properties / model / enum
      Previous value: -[
      -  "suno-v4",
      -  "suno-v4.5",
      -  "suno-v4.5-all",
      -  "suno-v4.5-plus",
      -  "suno-v5",
      -  "suno-v5.5"
      -]New value: +[
      +  "suno-v4",
      +  "suno-v4.5",
      +  "suno-v4.5-all",
      +  "suno-v4.5-plus",
      +  "suno-v5",
      +  "suno-v5.5",
      +  "suno-v6",
      +  "suno-v6-mini",
      +  "suno-v6-wild"
      +]
  2. Changed10 schema fields changedv0.3.5
    • addedInput schema / properties / audio_weight / maximum
      Added value: +1
    • addedInput schema / properties / audio_weight / minimum
      Added value: +0
    • addedInput schema / properties / lyrics / maxLength
      Added value: +5000
    • addedInput schema / properties / prompt / maxLength
      Added value: +5000
    • addedInput schema / properties / style / maxLength
      Added value: +1000
    • addedInput schema / properties / style_weight / maximum
      Added value: +1
    • addedInput schema / properties / style_weight / minimum
      Added value: +0
    • addedInput schema / properties / title / maxLength
      Added value: +80
    • addedInput schema / properties / weirdness_constraint / maximum
      Added value: +1
    • addedInput schema / properties / weirdness_constraint / minimum
      Added value: +0
  3. Changed12 schema fields changedv0.3.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / persona_type / anyOf
      Added value: +[
      +  {
      +    "const": "style",
      +    "type": "string"
      +  },
      +  {
      +    "const": "voice",
      +    "type": "string"
      +  }
      +]
    • removedInput schema / properties / persona_type / enum
      Removed value: -[
      -  "style",
      -  "voice"
      -]
    • removedInput schema / properties / persona_type / type
      Removed value: -"string"
    • addedInput schema / properties / poll_interval_ms / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / timeout_ms / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / vocal_gender / anyOf
      Added value: +[
      +  {
      +    "const": "male",
      +    "type": "string"
      +  },
      +  {
      +    "const": "female",
      +    "type": "string"
      +  }
      +]
    • removedInput schema / properties / vocal_gender / enum
      Removed value: -[
      -  "male",
      -  "female"
      -]
    • removedInput schema / properties / vocal_gender / type
      Removed value: -"string"
    • addedInput schema / properties / vocal_mode / anyOf
      Added value: +[
      +  {
      +    "const": "auto_lyrics",
      +    "type": "string"
      +  },
      +  {
      +    "const": "exact_lyrics",
      +    "type": "string"
      +  },
      +  {
      +    "const": "instrumental",
      +    "type": "string"
      +  }
      +]
    • removedInput schema / properties / vocal_mode / enum
      Removed value: -[
      -  "auto_lyrics",
      -  "exact_lyrics",
      -  "instrumental"
      -]
    • removedInput schema / properties / vocal_mode / type
      Removed value: -"string"
  4. Changed14 schema fields changedv0.2.4
    • addedInput schema / properties / audio_weight / description
      Added value: +"Audio weight (0-1)."
    • addedInput schema / properties / callback_url / description
      Added value: +"Webhook URL for async notifications."
    • addedInput schema / properties / lyrics / description
      Added value: +"Exact cover lyrics to sing."
    • addedInput schema / properties / negative_tags / description
      Added value: +"Styles to avoid."
    • addedInput schema / properties / persona_id / description
      Added value: +"Persona ID."
    • addedInput schema / properties / persona_type / description
      Added value: +"Persona type."
    • addedInput schema / properties / prompt / description
      Added value: +"Cover brief for automatic lyrics."
    • addedInput schema / properties / style / description
      Added value: +"Music style."
    • addedInput schema / properties / style_weight / description
      Added value: +"Style adherence weight (0-1)."
    • addedInput schema / properties / title / description
      Added value: +"Music title."
    • addedInput schema / properties / upload_url / description
      Added value: +"URL of the audio file to cover."
    • addedInput schema / properties / vocal_gender / description
      Added value: +"Vocal gender."
    • addedInput schema / properties / vocal_mode / description
      Added value: +"Vocal generation mode."
    • addedInput schema / properties / weirdness_constraint / description
      Added value: +"Weirdness constraint (0-1)."
  5. Changed9 schema fields changedv0.1.2
    • addedInput schema / properties / callback_url / type
      Added value: +"string"
    • addedInput schema / properties / lyrics / type
      Added value: +"string"
    • addedInput schema / properties / negative_tags / type
      Added value: +"string"
    • addedInput schema / properties / persona_id / type
      Added value: +"string"
    • addedInput schema / properties / prompt / type
      Added value: +"string"
    • addedInput schema / properties / style / type
      Added value: +"string"
    • addedInput schema / properties / title / type
      Added value: +"string"
    • addedInput schema / properties / upload_url / type
      Added value: +"string"
    • changedInput schema / required
      Previous value: -[
      -  "vocal_mode"
      -]New value: +[
      +  "upload_url",
      +  "vocal_mode"
      +]
  6. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits itself. It only mentions the return values but does not disclose that this is likely an asynchronous task creation with polling/wait options, that it incurs cost, or that it requires authentication. The existence of wait, timeout_ms, poll_interval_ms, and callback_url parameters implies asynchronous behavior, but the description is silent on it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

The description is a single sentence that quickly states the action and the return type. It is short and front-loaded with the core purpose, with no wasted words.

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?

For a complex tool with 18 parameters, no annotations, and no output schema, the description is inadequate. It mentions the return values but does not explain how to use the task id, whether to wait, what statuses mean, or any usage constraints. An agent would need to rely on the schema, which still leaves gaps.

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?

The schema already describes the parameters with 89% coverage. The description adds no parameter-specific meaning beyond the name 'cover audio', which is already apparent from the tool name. Since schema coverage is high, the baseline score of 3 is appropriate.

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?

The description clearly states the tool creates a Suno task for covering audio on RunAPI and lists the return values. It uses a specific verb ('Create') and resource ('Suno task'), and the 'cover audio' qualifier distinguishes it from many sibling tools, though it does not explicitly name alternatives.

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 guidance is provided about when to use this tool versus alternatives like convert_audio or remaster_audio. There is no mention of prerequisites, context, or exclusion criteria, so an agent is left without direction on tool selection.

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