Skip to main content
Glama
Sign In
SunoMCP

SunoMCP

by AceDataCloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

suno_upload_cover

Creates an AI cover from uploaded audio, re-arranging your own music into a different style.

Instructions

Create an AI cover of an uploaded audio (your own music).

Similar to suno_cover_music but works with audio you uploaded via
suno_upload_audio. Re-arranges your music in a different style.

Use this when:
- You uploaded your own music and want a cover in a different style
- You want to hear your song re-interpreted by AI

Returns:
    Task ID and the cover audio information.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "audio_id": "<audio_id>"
    },
    "name": "suno_upload_cover"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNoModel version to use.chirp-v5-5
styleNoTarget music style for the cover.
audio_idYesID of the uploaded audio to create a cover of. Must be an audio uploaded via suno_upload_audio.
persona_idNoPersona ID for a specified-voice cover. Private voices require the audio_id returned by suno_upload_audio with this same persona_id in standard mode. Keep voice creation, upload and cover on the same service channel. No extra vocal_gender is needed; gender cannot replace the voice ID.
audio_weightNoAdvanced parameter for cover operations. Controls how much the original audio influences the cover generation.
callback_urlNoWebhook callback URL for asynchronous notifications.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.24
    • addedInput schema / properties / persona_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Persona ID for a specified-voice cover. Private voices require the audio_id returned by suno_upload_audio with this same persona_id in standard mode. Keep voice creation, upload and cover on the same service channel. No extra vocal_gender is needed; gender cannot replace the voice ID.",
+  "title": "Persona Id"
+}
  2. Changed1 schema field changedv0.1.18
    • changedInput schema / properties / model / enum
      Previous value: -[
-  "chirp-v3-0",
-  "chirp-v3-5",
-  "chirp-v4",
-  "chirp-v4-5",
-  "chirp-v4-5-plus",
-  "chirp-v5",
-  "chirp-v5-5"
-]New value: +[
+  "chirp-v6",
+  "chirp-v6-wild",
+  "chirp-v6-mini",
+  "chirp-v3-0",
+  "chirp-v3-5",
+  "chirp-v4",
+  "chirp-v4-5",
+  "chirp-v4-5-plus",
+  "chirp-v5",
+  "chirp-v5-5"
+]
  3. Addedv0.1.5
  4. Removedv0.1.3
  5. Changed1 schema field changedv0.1.1
    • addedInput schema / properties / audio_weight
      Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Advanced parameter for cover operations. Controls how much the original audio influences the cover generation.",
+  "title": "Audio Weight"
+}
  6. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. It discloses that the tool returns a Task ID and cover audio information, implying asynchronous generation, but does not cover permissions, cost, latency, or what happens to the source audio; that is minimally adequate but not rich.

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?

The purpose and sibling distinction are front-loaded, and the 'Use this when' bullets make the guidance easy to scan. There is minor repetition of the ownership idea ('your own music' and 'uploaded your own music'), but the description is otherwise efficient.

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?

The tool has an output schema, so the description need not explain return structure in depth; it still briefly mentions the Task ID and cover audio info. Combined with complete parameter schema coverage, the description gives enough context for correct invocation, though it could add a note about async task polling for completeness.

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 description coverage is 100%, so the schema already documents all six parameters, including audio_id, style, model, persona_id, audio_weight, and callback_url. The description only reinforces the audio_id origin requirement and adds no new parameter detail beyond the schema, which is the expected baseline when schema coverage is complete.

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 states a specific verb and resource: 'Create an AI cover of an uploaded audio (your own music).' It also explicitly distinguishes itself from the sibling suno_cover_music by explaining that it works with audio uploaded via suno_upload_audio, so an agent can select it without opening either schema.

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

Usage Guidelines4/5

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

The 'Use this when' bullets give clear conditions: uploaded your own music, want a different style, or want an AI re-interpretation. It names suno_cover_music as the similar alternative but does not explicitly state when not to use this tool, leaving the inverse selection rule implied.

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