Skip to main content
Glama

producer_swap_vocals

Replace vocals in one song with vocals from another to create vocal mashups by combining the instrumental track from the base audio with the vocal track from the swap audio.

Instructions

Swap the vocals of one song with vocals from another song.

Takes the instrumental track from the base audio and combines it with
the vocal track from the swap audio.

Use this when:
- You want to combine vocals from one song with instrumentals from another
- You want to hear how different vocals sound over the same beat
- You're creating a vocal mashup

Returns:
    Task ID and the swapped audio information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
audio_idYesID of the base audio whose vocals will be replaced.
swap_audio_idYesID of the audio whose vocals to use as replacement.
callback_urlNoWebhook callback URL for asynchronous notifications.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations, so description must disclose behavior. It explains the combination logic: keeps instrumental from base, adds vocal from swap. Mentions async callback and returns Task ID and audio info.

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?

Well-structured with short sentences and bullet points. Every sentence adds value, no fluff.

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?

Description covers inputs, process, and output. Missing prerequisites like audio must be uploaded first, but output schema exists to document return values.

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?

Schema coverage is 100% and description adds meaning: explains audio_id as base audio and swap_audio_id as source of vocals. Also clarifies callback_url for async notifications.

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?

Description clearly states the tool swaps vocals between two songs, using instrumental from base and vocal from swap. It distinguishes from sibling 'producer_swap_instrumentals' by focusing on vocals.

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?

Explicit 'Use this when' bullets provide clear scenarios. No explicit when-not-to-use or alternatives, but the sibling list implies differentiation.

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