Skip to main content
Glama

suno_upload_audio

Upload an external audio file to Suno to use it as a base for extending or creating covers of your music.

Instructions

Upload an external audio file to Suno for use in subsequent operations.

Uploads audio from a URL so it can be used with actions like upload_extend
and upload_cover, which allow you to extend or create covers of your own music.

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

After uploading, use the returned audio_id with suno_upload_extend or
suno_upload_cover actions.

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?

No annotations provided, so description carries full burden. It discloses that the audio URL must be publicly accessible and that it returns an audio ID. However, it omits details like file format constraints, size limits, or whether uploads are overwritten or create new entries.

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 moderately concise with a clear first sentence, bullet list for usage, and returns section. It is well-structured but could be slightly more succinct.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the existence of an output schema, the description adequately covers purpose, usage, and follow-up. However, it lacks details on file format, size limits, and error handling, leaving some gaps for a simple upload tool.

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 input schema already describes the audio_url parameter with details on accessibility. The tool description does not add additional semantic meaning beyond what the schema provides, so baseline of 3 is appropriate.

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 verb (upload) and resource (external audio file to Suno). It distinguishes from siblings by specifying that this is for importing audio to be used with upload_extend and upload_cover, two specific sibling tools.

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?

Provides explicit when-to-use scenarios with three bullet points and indicates the follow-up actions (use returned audio_id with specific sibling tools). Does not explicitly state when not to use, but the positive guidance is clear.

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

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