ACE Music MCP Server by useapi.net (third-party)

Upload audio or an image

acemusic_upload_file

Upload an audio file (mp3, wav, flac, ogg, m4a, aac; up to 8 min) as a Library song ACE Music transcribes, usable as a reference songId, or an image (jpg, png, webp; up to 10 MB) usable in acemusic_create_song images. From a public https url or as contentBase64 (small files). Returns the songId or image id, valid on that account only. POST /files.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "acemusic_upload_file"
  }
}

Input Schema

Name	Required	Description
`url`	No	A public https URL of the file.
`email`	No	The account to upload to (a file works only there). Default: any healthy account.
`title`	No	A title for an audio upload.
`mimeType`	No	The file's type. Default: from the url's answer.
`contentBase64`	No	The file content, base64-encoded (instead of url).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already disclose a non-read-only, non-idempotent, open-world write. The description adds genuinely new behavior: duration and size limits, accepted formats, and the crucial scoping fact that the returned id is valid on that account only. It does not discuss overwrite/duplicate handling or whether uploads consume quota.

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?

One dense but well-ordered sentence moves from what is uploaded, to formats and limits, to where it comes from, to what is returned — plus a short endpoint note. Every clause carries information, though the opening sentence is heavy enough to be slightly hard to scan.

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?

With no output schema, the description correctly states the return value (songId or image id), and it covers format, size, source, and account scoping for a 5-parameter upload tool. Only secondary behavior such as duplicate handling or post-upload processing status is left unstated.

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 all five parameters are already documented, making the baseline 3. The description adds only the 'public https' requirement and the 'small files' caveat for contentBase64, which are marginal refinements over the schema text rather than new meaning.

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?

States a specific verb (upload) and two concrete resources (audio file, image) with enumerated formats, and names the downstream uses (reference songId, images for acemusic_create_song). An agent can immediately distinguish it from create_song, get_song, or download_song.

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?

Gives clear context for choosing the two upload paths (public https URL vs contentBase64 for small files) and the constraints that decide eligibility (8 min audio, 10 MB image). It stops short of explicit when-not-to-use guidance or stating what happens on re-upload of the same asset.

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

All ACE Music MCP Server by useapi.net (third-party) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?