Skip to main content
Glama

extend_music

Create a Suno task to extend an existing track, returning a task ID and output URLs. Inherit source parameters or set custom ones.

Instructions

Create a Suno task on RunAPI (extend music). 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.
styleNoStyle preset. Required in custom parameter mode.
titleNoSong title. Required in custom parameter mode.
lyricsNoExact lyrics. Only allowed when extending uploaded audio in custom parameter mode.
promptNoExtension brief. Cannot be combined with lyrics.
task_idNoSource task ID to extend. Provide one of task_id, audio_id, audio_url, or upload_url.
audio_idNoSource audio ID to extend. Provide one of task_id, audio_id, audio_url, or upload_url.
audio_urlNoSource audio URL to extend. Provide one of task_id, audio_id, audio_url, or upload_url.
persona_idNoPersona ID.
timeout_msNo
upload_urlNoUploaded source audio URL to extend. Provide one of task_id, audio_id, audio_url, or upload_url.
continue_atNoSeconds into the source to continue from. Required in custom parameter mode.
audio_weightNoAudio weight (0-1).
callback_urlNoWebhook URL for async notifications.
instrumentalNoWhen true, generate without vocals.
persona_typeNoPersona type.
style_weightNoStyle adherence weight (0-1).
vocal_genderNoVocal gender.
negative_tagsNoStyles to avoid.
parameter_modeYesInherit the source track's parameters (source) or supply custom ones (custom).
poll_interval_msNo
weirdness_constraintNoWeirdness constraint (0-1).
Behavior2/5

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

Description mentions returned fields (task id, status, output URLs) but does not disclose behavioral traits like asynchronicity, destructive potential, authentication needs, or rate limits. With no annotations, the description carries full burden but provides minimal insight.

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?

Single sentence with no filler. Efficiently states the core function and output, though a bit terse.

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?

Tool has 23 parameters and no output schema or annotations. Description is far too brief to cover the complexity, omitting crucial details like parameter_mode distinction and source specification requirements.

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 91%, so the schema already documents most parameters. The description adds no extra meaning beyond what the schema provides. Baseline 3 is appropriate.

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?

Description states 'Create a Suno task on RunAPI (extend music)', clearly identifying the action and resource. The parenthetical 'extend music' distinguishes it from sibling tools like text_to_music or text_to_sound.

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 versus alternatives such as cover_audio or blend_lyrics. Only implicit usage is suggested by the tool name and description.

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