Skip to main content
Glama
AceDataCloud

SunoMCP

by AceDataCloud
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

suno_mashup_music

Blend two songs into a single mashup track by combining their audio elements. Provide creative direction for arrangement and balance to produce a cohesive musical mix.

Instructions

Create a musical mashup by blending multiple songs together.

Combines elements from multiple generated songs into a single cohesive
mashup track. Different from lyrics mashup - this blends the actual audio.

Use this when:
- You want to blend two or more songs together musically
- You're creating a DJ-style mashup
- You want to combine melodies from different songs

Returns:
    Task ID and the mashup audio information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNoModel version to use.chirp-v5-5
styleNoOptional target music style for the mashup.
titleNoOptional title for the mashup.
promptYesRequired creative direction for blending the tracks, such as the desired arrangement, mood, and balance between sources.
callback_urlNoWebhook callback URL for asynchronous notifications.
instrumentalNoIf true, generate an instrumental mashup without vocals.
mashup_audio_idsYesExactly two audio IDs to mash up together.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+]
  2. Changed8 schema fields changedv0.1.11
    • addedInput schema / properties / instrumental
      Added value: +{
+  "default": false,
+  "description": "If true, generate an instrumental mashup without vocals.",
+  "title": "Instrumental",
+  "type": "boolean"
+}
    • changedInput schema / properties / mashup_audio_ids / description
      Previous value: -"List of audio IDs to mashup together. Provide 2 or more song IDs."New value: +"Exactly two audio IDs to mash up together."
    • addedInput schema / properties / mashup_audio_ids / maxItems
      Added value: +2
    • addedInput schema / properties / mashup_audio_ids / minItems
      Added value: +2
    • addedInput schema / properties / prompt
      Added value: +{
+  "description": "Required creative direction for blending the tracks, such as the desired arrangement, mood, and balance between sources.",
+  "title": "Prompt",
+  "type": "string"
+}
    • addedInput schema / properties / style
      Added value: +{
+  "default": "",
+  "description": "Optional target music style for the mashup.",
+  "title": "Style",
+  "type": "string"
+}
    • addedInput schema / properties / title
      Added value: +{
+  "default": "",
+  "description": "Optional title for the mashup.",
+  "title": "Title",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "mashup_audio_ids"
-]New value: +[
+  "mashup_audio_ids",
+  "prompt"
+]
  3. Addedv0.1.5
  4. Removedv0.1.3
  5. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Since no annotations are provided, the description must carry the full burden of behavioral disclosure. It mentions it returns a Task ID and mashup audio information, which is useful. However, it does not disclose that the operation creates new audio (a creative generation action), whether it consumes credits, or any other behavioral traits. The asynchronous nature is implied by Task ID but not fully explained. The description is 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 description is relatively concise, using bullet points and a short returns section. The main purpose is front-loaded. However, the 'Returns' section is redundant with the output schema (which exists per context signals), and the 'Use this when' section could be more compact. Still, it is efficient and easy to scan.

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?

Given the tool's moderate complexity (7 parameters, but only 2 required) and the presence of an output schema, the description covers the essential purpose and usage scenarios. The required parameter 'mashup_audio_ids' is clearly constrained to exactly two audios in the schema, and the description mentions 'multiple songs'. The only missing element is a mention of any prerequisites (e.g., the audio IDs must come from previously generated songs), but this is not critical.

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%, meaning every parameter is described in the schema. The tool description adds some context for the 'prompt' parameter by describing it as 'creative direction for blending the tracks', which adds meaning beyond the schema's generic description. However, most parameters like 'model', 'style', 'title', 'instrumental', and 'callback_url' are already well-documented in the schema, so the description adds limited additional value.

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 clearly states the tool's function: creating a musical mashup by blending multiple songs together. It explicitly distinguishes itself from 'lyrics mashup' by specifying it blends the actual audio, which is crucial given the sibling tool suno_mashup_lyrics. The use of specific verb 'create', resource (musical mashup), and clear distinction from alternatives makes the purpose highly clear.

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 description provides a 'Use this when' list with three specific scenarios: blending two or more songs musically, creating DJ-style mashups, and combining melodies from different songs. It also implicitly differentiates from lyrics mashup by mentioning the difference. However, it does not explicitly state when NOT to use it or directly reference the alternative suno_mashup_lyrics by name, which would be more complete.

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

Install Server

Other Tools