Skip to main content
Glama
runapi-ai

suno-mcp

by runapi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

add_samples

Create a Suno task to add a sample from an audio URL at a chosen start and end time. Returns a task ID, status, and output URLs.

Instructions

Create a Suno task on RunAPI (add samples). Returns a task id, status, and output URLs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
waitNoPoll until the task reaches a terminal status.
modelNoRunAPI model slug for this model line.
promptNoOptional description of the sample to add. Declared type: string.
audio_urlYesURL of the audio file to sample. Declared type: string.
timeout_msNo
end_secondsYesEnd of the sample range in seconds; must exceed start_seconds. Declared type: number.
callback_urlNoWebhook URL for async notifications. Declared type: string.
start_secondsYesStart of the sample range in seconds. Declared type: number.
poll_interval_msNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.4.0
    • addedInput schema / additionalProperties
      Added value: +{}
    • changedInput schema / properties / audio_url / description
      Previous value: -"URL of the audio file to sample."New value: +"URL of the audio file to sample. Declared type: string."
    • changedInput schema / properties / callback_url / description
      Previous value: -"Webhook URL for async notifications."New value: +"Webhook URL for async notifications. Declared type: string."
    • changedInput schema / properties / end_seconds / description
      Previous value: -"End of the sample range in seconds; must exceed start_seconds."New value: +"End of the sample range in seconds; must exceed start_seconds. Declared type: number."
    • removedInput schema / properties / end_seconds / minimum
      Removed value: -0
    • removedInput schema / properties / model / enum
      Removed value: -[
-  "suno-v4",
-  "suno-v4.5",
-  "suno-v4.5-plus",
-  "suno-v5",
-  "suno-v5.5"
-]
    • changedInput schema / properties / prompt / description
      Previous value: -"Optional description of the sample to add."New value: +"Optional description of the sample to add. Declared type: string."
    • changedInput schema / properties / start_seconds / description
      Previous value: -"Start of the sample range in seconds."New value: +"Start of the sample range in seconds. Declared type: number."
    • removedInput schema / properties / start_seconds / minimum
      Removed value: -0
  2. Changed1 schema field changedv0.3.5
    • addedInput schema / properties / prompt
      Added value: +{
+  "description": "Optional description of the sample to add.",
+  "type": "string"
+}
  3. Addedv0.3.2

TDQS

C2.8/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose that the tool returns a task id, status, and output URLs, which is useful since there is no output schema. But it omits critical async behavior, polling semantics (wait, timeout_ms, poll_interval_ms), callback handling, and permission or error characteristics.

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 two short sentences with no wasted words, and the core action is front-loaded. It is appropriately sized, though it could use slightly more specificity without becoming bloated.

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

Completeness2/5

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

For a 9-parameter tool with no annotations and no output schema, the description is too thin. It provides only a minimal return description and omits usage context, parameter interpretation, and behavioral details that an agent needs to invoke the tool correctly.

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 78%, which is high, so the schema already documents most parameters. The description adds no parameter meaning beyond what the schema provides, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (Create) and resource (Suno task), with a parenthetical action label (add samples). However, it does not explain what adding samples actually does or distinguish the tool from other task-creating siblings such as convert_audio or extend_music.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no conditions for selection. The description only states what the tool does, leaving the agent to infer usage from the tool name alone.

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

Deploy Server

Other Tools