Skip to main content
Glama

producer_upload_audio

Upload an external audio URL to import music for processing with Producer. Use the returned audio ID for extension, remixing, cover, or variation.

Instructions

Upload an external audio file for use in subsequent operations.

Uploads audio from a URL so it can be used with actions like extend,
cover, variation, swap_vocals, and swap_instrumentals.

Use this when:
- You have your own music you want to process with Producer
- You want to use an external audio as a base for operations
- You need to import audio into Producer's system

After uploading, use the returned audio_id with other Producer tools.

Returns:
    Upload result with audio ID for use in subsequent operations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
audio_urlYesPublic URL of the audio file to upload. The URL must be directly accessible (CDN link, cloud storage URL, etc.).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Discloses the basic behavior (upload from URL, return audio_id), but lacks details on supported file formats, size limits, or potential errors. No annotations are present to supplement these gaps.

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 a summary line, explanatory paragraph, bullet list, and return note. Every sentence serves a purpose, and the length is appropriate for the tool's simplicity.

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 single parameter and straightforward operation, the description covers purpose, usage, and return value adequately. Could mention constraints like file types or size limits for full completeness.

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%, and the description merely reiterates that the parameter is a URL for external audio. It adds no new semantic information beyond the schema's own description.

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?

Clearly states the action (upload) and resource (external audio file). Lists specific downstream operations that can use the uploaded audio, distinguishing it from sibling tools which are generative or transformative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly provides three 'Use this when' scenarios and instructs to use the returned audio_id with other tools. Direction on when to use is clear and actionable.

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