suno-mcp

create_mashup

Combine two audio tracks into a mashup using Suno's AI music models. Choose vocal mode (auto lyrics, exact lyrics, instrumental) and receive task ID, status, and output URLs.

Instructions

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

Input Schema

TableJSON Schema

Name	Required	Description
`wait`	No	Poll until the task reaches a terminal status.
`model`	No	RunAPI model slug for this model line.
`style`	No	Music style.
`title`	No	Music title.
`lyrics`	No	Exact mashup lyrics to sing.
`prompt`	No	Mashup brief for automatic lyrics.
`persona_id`	No	Persona ID.
`timeout_ms`	No
`vocal_mode`	Yes	Vocal generation mode.
`audio_weight`	No	Audio weight (0-1).
`callback_url`	No	Webhook URL for async notifications.
`persona_type`	No	Persona type.
`style_weight`	No	Style adherence weight (0-1).
`vocal_gender`	No	Vocal gender.
`upload_url_list`	Yes	Two audio URLs to mashup.
`poll_interval_ms`	No
`weirdness_constraint`	No	Weirdness constraint (0-1).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.3.6Sep 18, 2026

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"
+]

Changed10 schema fields changedv0.3.5Sep 11, 2026
- 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
```

Changed12 schema fields changedv0.3.2Aug 21, 2026

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"
```

Changed15 schema fields changedv0.2.4Jul 29, 2026
- 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 mashup lyrics to sing."
```
- 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: +"Mashup 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_list / description
```
Added value: +"Two audio URLs to mashup."
```
- addedInput schema / properties / upload_url_list / maxItems
```
Added value: +2
```
- addedInput schema / properties / upload_url_list / minItems
```
Added value: +2
```
- 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)."
```

Changed1 schema field changedv0.1.9Jul 13, 2026

changedInput schema / required

Previous value: -[
-  "vocal_mode",
-  "upload_url_list"
-]New value: +[
+  "upload_url_list",
+  "vocal_mode"
+]

Changed6 schema fields changedv0.1.2Jun 23, 2026
- addedInput schema / properties / callback_url / type
```
Added value: +"string"
```
- addedInput schema / properties / lyrics / 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"
```
First observedv0.1.0Jun 23, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations, the description itself must carry behavioral weight; it does state the core side effect ('Create a Suno task') and a useful outcome ('Returns a task id, status, and output URLs'). It does not disclose async/polling behavior, webhook interaction, or any limitations, but the minimal create-and-return contract is at least present.

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?

A single front-loaded sentence communicates the core action and return values with no filler. Every word earns its place, and the parenthetical 'create mashup' reinforces the function name without bloating the text.

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?

This is a complex tool (17 parameters, no output schema, no annotations) but the description only provides a one-line contract. Missing context includes the connection between vocal_mode and lyrics/prompt, how wait/callback_url affect the returned task, and what 'output URLs' refer to; an agent would need to reason from the schema alone for nearly everything.

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 coverage is 88%, so the baseline of 3 applies: the schema already documents all parameters, including required 'upload_url_list' (exactly two URLs) and 'vocal_mode'. The description adds no parameter-level meaning, but it doesn't need to because the schema carries the burden.

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 names a specific verb and resource ('Create a Suno task on RunAPI') and clarifies the specific operation with '(create mashup)', which distinguishes it from siblings like text_to_music or cover_audio. However, it doesn't explain what makes a 'mashup' task distinct from related Suno operations beyond the name.

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?

There is no when-to-use guidance, and no sibling alternatives are mentioned. An agent must infer from the name and the 'mashup' parenthetical that this is for combining two audio files, rather than being told when to choose it over blend_lyrics, cover_audio, or text_to_music.

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

create_mashup

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools