Skip to main content
Glama

extend_music

Creates a Suno task to extend an existing music track using an audio URL or ID, with customizable style, lyrics, and continuation settings.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
styleNo
titleNo
lyricsNo
promptNo
task_idNo
audio_idNo
audio_urlNo
persona_idNo
upload_urlNo
continue_atNo
audio_weightNo
callback_urlNo
instrumentalNo
persona_typeNo
style_weightNo
vocal_genderNo
negative_tagsNo
parameter_modeNo
weirdness_constraintNo
waitNoPoll until the task reaches a terminal status.
timeout_msNo
poll_interval_msNo
modelNoRunAPI model slug for this model line.
Behavior2/5

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

With no annotations, the description should disclose behavioral traits like asynchronicity, polling requirements, and auth needs. Only mentions returns but not that it is asynchronous or requires waiting.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, concise but omits crucial detail. Does not front-load essential info like required parameters or workflow.

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

Completeness1/5

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

Given 23 parameters, no output schema, no annotations, and many sibling tools, this description is severely incomplete. It fails to provide enough context for correct agent invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 9% (2 of 23 parameters described). The description adds no parameter context despite 23 params; does not explain key parameters like audio_url, task_id, or prompt.

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

Purpose4/5

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

The description states 'Create a Suno task on RunAPI (extend music)' and mentions returns, indicating it extends existing music. It distinguishes from siblings like text_to_music and cover_audio but does not fully define 'extend music' versus create_mashup.

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?

No guidance on when to use this tool vs alternatives (e.g., text_to_music, cover_audio). Does not specify prerequisites or typical use cases.

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/runapi-ai/suno-mcp'

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