Skip to main content
Glama

mashup_songs

Idempotent

COSTS CREDITS (see list_song_tools): state the price and get the user's confirmation first. Blend two of the user's songs into a new one (Rao/Suno). mode "simple": describe the result in description; mode "custom": your lyrics + style + title. Returns an id; poll get_generation.

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": {
      "id": "<id>",
      "secondId": "<secondId>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "mashup_songs"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSource song id (songs[].id from get_generation / list_songs / save_upload).
modeNosimple
styleNocustom mode.
titleNocustom mode.
lyricsNocustom mode: lyrics.
versionNoRao/Suno version id (list_song_tools.recreate.versions); omit for the default. Sets the price.
secondIdYesThe second song id (must also be the user's).
descriptionNosimple mode: one-line description (required unless instrumental).
vocalGenderNo
instrumentalNo
idempotencyKeyYes8-64 chars [A-Za-z0-9._:-]. Same rules as generate_music: stable per logical request, resend the same key + params after a timeout instead of paying twice; new key when anything changes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations cover idempotency and non-destructiveness, and the description adds the genuinely non-obvious traits: this consumes credits, the price depends on the version parameter, and the call is asynchronous returning an id to poll. It does not quantify costs or state failure/refund behavior, but the value added beyond annotations is substantial.

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 credit warning is front-loaded and every clause carries information, with no filler. The telegraphic phrasing ("mode \"simple\": describe the result in description") is compact but slightly cryptic on first read.

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?

For an 11-parameter, async, credit-consuming tool with no output schema, the description supplies the return shape (an id), the follow-up tool, and the cost/confirmation gate. Only edge cases such as what happens when a blend fails or how long generation takes are unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 73% schema coverage the baseline is 3, and the description earns more by explaining the mode-conditional meaning of description/lyrics/style/title and that version selects the price. It leaves vocalGender and instrumental unexplained, which the schema only partially covers.

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?

"Blend two of the user's songs into a new one" is a specific verb+resource, and naming the provider (Rao/Suno) plus the two modes makes it distinguishable from siblings like generate_music, add_vocals, and add_instrumental. An agent can tell what this produces without opening the 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?

It gives an explicit pre-call ritual (state the price from list_song_tools and get confirmation) and a post-call step (poll get_generation), plus mode-selection guidance: simple uses a description, custom uses lyrics+style+title. It never says when to prefer this over generate_music or extend_song, so it falls short of full when/when-not coverage.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.