Skip to main content
Glama
AceDataCloud

SunoMCP

by AceDataCloud
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

suno_upload_audio

Upload audio from a URL to Suno for extending or covering your own music. Use the returned audio ID with Suno extension or cover actions.

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

Tool Definition Quality

A4/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It states the input and return value but omits details like file size limits, supported formats, or idempotency. Adequate for a simple upload.

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?

Concise and well-structured: purpose first, then usage guidelines, then return value. No wasted words.

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 (1 parameter, output schema exists), the description adequately explains the workflow and return value. Could be slightly more detailed on output, but not necessary.

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 adds minimal new information beyond the schema's own description of the audio_url parameter. 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?

Explicitly states 'Upload an external audio file to Suno' and distinguishes from siblings like suno_upload_extend and suno_upload_cover by noting that this is the prerequisite step for those operations.

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?

Clearly lists three scenarios for when to use this tool and mentions the follow-up actions. However, it does not explicitly state when NOT to use it.

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