Skip to main content
Glama

suno_samples_music

Add AI-generated samples to uploaded audio. Specify start and end times to enhance tracks with loops or motifs.

Instructions

Add AI-generated samples to uploaded audio.

Takes your uploaded audio and adds AI-generated musical samples
within the specified time range.

Use this when:
- You want to add sample loops or motifs to existing music
- You need to enhance a track with additional musical elements
- You want to add AI-generated samples to a specific section

Returns:
    Task ID and the audio with samples added.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
audio_idYesID of the uploaded audio to add samples to. Must be uploaded via suno_upload_audio.
samples_startNoStart time in seconds for adding samples. Default is 0.
samples_endNoEnd time in seconds for adding samples. Must be less than total song duration.
modelNoModel version to use.chirp-v5-5
callback_urlNoWebhook callback URL for asynchronous notifications.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so description carries full burden. It states the tool adds samples (mutation) but doesn't disclose potential side effects, limitations, or prerequisites beyond uploading audio. Minimal behavioral context.

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?

Description is concise with two paragraphs and bullet points. Front-loaded with main action. Could be slightly more compact but overall efficient.

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 5 parameters, output schema, and sibling variety, the description provides basic overview but lacks details on task retrieval, error cases, or how output can be used. Adequate but not comprehensive.

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 description coverage is 100%, so baseline is 3. The description adds context about the time range but mostly restates schema info. No significant additional meaning beyond schema.

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 adds AI-generated samples to uploaded audio, using a specific verb and resource. It distinguishes itself from siblings like generation or concatenation 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?

The 'Use this when' bullet points provide explicit guidance on when to use the tool. It lacks explicit when-not-to-use or alternatives, but the listed use cases are helpful.

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