Skip to main content
Glama
AceDataCloud

ProducerMCP

by AceDataCloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

producer_upload_audio

Import audio from a public URL for use in music production tasks. Get an audio ID to apply extensions, covers, variations, or vocal/instrumental swaps.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.13
  2. Removedv0.1.12
  3. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

The description explains that the tool uploads audio from a URL and returns an audio_id. It mentions the URL must be directly accessible, which is a useful constraint. Without annotations, the description provides reasonable behavioral context for a simple upload operation.

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 relatively concise with a clear structure: main verb, explanation, use cases, and return value. It is front-loaded with the key purpose. Could be slightly tighter but overall efficient.

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 tool's simplicity (one parameter, no nested objects) and the presence of an output schema, the description covers the workflow adequately. It explains how the output (audio_id) is used with sibling tools, making it contextually complete.

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?

The single parameter 'audio_url' has 100% schema coverage, and the description adds extra guidance that the URL must be directly accessible. This adds semantic value beyond the schema's basic 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?

The description clearly states the tool uploads an external audio file for subsequent operations, and distinguishes it from sibling tools that process audio. It specifies the output (audio_id) and usage with actions like extend, cover, etc.

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 lists specific scenarios when to use the tool (e.g., when you have your own music, want to use external audio). While it doesn't explicitly state when not to use it, the context makes it clear that this is the import tool and siblings are for processing.

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

Deploy Server

Other Tools