Skip to main content
Glama

producer_cover_music

Transform an existing song into a cover or remix with a different genre, mood, or arrangement while preserving the core melody and lyrics.

Instructions

Create a cover or remix version of an existing song in a different style.

This generates a new version of a song with a different arrangement, genre,
or mood while keeping the core melody and lyrics.

Use this when:
- You want to hear a song in a different genre
- You want an acoustic/unplugged version of an electronic song
- You want to remix a song with a different vibe

Returns:
    Task ID and the cover audio information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
audio_idYesID of the audio to create a cover of. This is the 'id' field from a previous generation.
promptNoDescription of how you want the cover to sound. Examples: 'acoustic unplugged version', 'jazz lounge style', '80s synthwave remix'
styleNoTarget music style for the cover. Examples: 'jazz, smooth, saxophone', 'acoustic folk, gentle guitar', 'electronic dance, high energy'
modelNoModel version to use for the cover.FUZZ-2.0
callback_urlNoWebhook callback URL for asynchronous notifications.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description must cover behavioral traits. It states it generates a new version and returns a Task ID and cover audio info. It does not disclose destruction, auth needs, or rate limits, but adds some context beyond the minimal.

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 well-structured with a clear first sentence and a bulleted usage list. It is concise without unnecessary details, though the return statement could be integrated.

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 presence of an output schema and 100% parameter coverage, the description is reasonably complete. It explains the tool's purpose and usage, though it could mention the relationship with producer_variation_music.

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 100%, so the description does not need to add much. It does not elaborate on parameters beyond what the schema already provides. The return description overlaps with output schema.

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 it creates a cover or remix version of an existing song in a different style, keeping core melody and lyrics. This distinguishes it from sibling tools like producer_variation_music (variations) and producer_generate_music (new music).

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 explicit usage scenarios: different genre, acoustic/unplugged version, remix with different vibe. It does not mention when not to use or directly compare to alternatives, but the scenarios are clear enough.

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/ProducerMCP'

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