Skip to main content
Glama

suno_mashup_music

Blend multiple songs into a single cohesive mashup track by combining their audio elements.

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
mashup_audio_idsYesList of audio IDs to mashup together. Provide 2 or more song IDs.
modelNoModel version to use.chirp-v5-5
callback_urlNoWebhook callback URL for asynchronous notifications.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations provided. Description mentions it blends audio and returns task ID/audio info, but lacks details on side effects, authorization needs, or rate limits. Minimal behavioral disclosure beyond basic operation.

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?

Concise at 5 sentences, front-loaded with action, then usage scenarios. No redundant information.

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?

Covers core purpose, usage scenarios, and return info. Distinguishes from related sibling. With output schema present, return details are sufficiently addressed.

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 descriptions cover 100% of parameters. Description adds context about blending actual audio, but parameters like mashup_audio_ids already have clear schema descriptions. Baseline score due to high schema coverage.

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?

Explicitly states it creates a musical mashup by blending audio from multiple songs. Distinguishes from lyrics mashup, which is a sibling tool (suno_mashup_lyrics).

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?

Provides specific 'Use this when' scenarios listing blending songs, DJ-style mashup, and melody combination. Does not explicitly state when not to use, but differentiation from lyrics mashup offers guidance.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AceDataCloud/SunoMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server