Skip to main content
Glama

suno_upload_audio

Upload external audio files to Suno using a public URL to extend tracks or create AI covers. Imports your music and returns an audio ID for subsequent operations.

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
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses the key behavioral trait that uploaded audio persists and creates a referenceable audio_id for future operations. However, lacks details on validation rules, file size limits, or error conditions that would help the agent handle failures.

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?

Well-structured with clear sections (purpose, use-when, next-steps, returns). Front-loaded with primary action. Slightly verbose in the 'Use this when' section where first two bullet points overlap, but every sentence contributes to workflow understanding.

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

Completeness5/5

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

Given the tool's role in a multi-step workflow (upload → extend/cover), description adequately explains the connection to sibling tools and the output schema implication (audio_id). With 100% param coverage and output schema existing, no additional context needed.

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 has 100% description coverage for audio_url ('Public URL...directly accessible'). Description mentions 'Uploads audio from a URL' which reinforces the parameter purpose but adds minimal semantic value beyond the schema's existing documentation of CDN/cloud storage requirements.

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 explicitly states 'Upload an external audio file to Suno' with specific verb and resource. It clearly distinguishes from generation tools by emphasizing 'external audio' and 'subsequent operations,' differentiating it from siblings like suno_generate_music.

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?

Contains explicit 'Use this when:' section with three specific scenarios. Explicitly names successor tools (suno_upload_extend, suno_upload_cover) and explains the workflow chain (upload → get audio_id → use in extend/cover), providing clear guidance on tool selection sequencing.

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

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