Skip to main content
Glama

extend_song

Idempotent

COSTS CREDITS (see list_song_tools): state the price and get the user's confirmation first. Continue a song from a point in time (Rao/Suno). Returns an id; poll get_generation.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "extend_song"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSource song id (songs[].id from get_generation / list_songs / save_upload).
styleNo
titleNo
lyricsNoLyrics for the new part (multi-line, [Verse]/[Chorus] tags allowed).
versionNoRao/Suno version id (list_song_tools.recreate.versions); omit for the default. Sets the price.
continueAtNoSecond to continue from; omit to continue from the end.
vocalGenderNo
instrumentalNo
idempotencyKeyYes8-64 chars [A-Za-z0-9._:-]. Same rules as generate_music: stable per logical request, resend the same key + params after a timeout instead of paying twice; new key when anything changes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations (openWorldHint, idempotentHint, destructiveHint=false), the description discloses that the call costs credits, that user confirmation is required before spending, and that the result is asynchronous and must be polled via get_generation. It does not cover failure or refund behavior, but it adds substantial context the annotations do not carry.

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?

Three short sentences with the highest-stakes information (credit cost and required confirmation) front-loaded, followed by the action and the follow-up step. Nothing is wasted and the ordering matches an agent's decision flow.

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?

With no output schema, the description correctly covers the return shape ('Returns an id; poll get_generation'). For a 9-parameter, credit-consuming mutation, the main missing element is what the operation does to the source song and how it relates to other editing tools, but the essentials for correct invocation are present.

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 56%, so the schema already documents most of the important fields (id, lyrics, version, continueAt, idempotencyKey). The description only gestures at the continuation point ('from a point in time') without adding format or defaulting semantics beyond what the schema states, so a 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?

The description states a specific verb and resource: 'Continue a song from a point in time (Rao/Suno).' That clearly separates it from siblings like restyle_song or replace_section, though it never names those alternatives explicitly, so the differentiation is implied rather than stated.

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?

It gives concrete operating instructions: state the price and get the user's confirmation first, consult list_song_tools for pricing, and poll get_generation after the call. It stops short of saying when not to use this tool versus other song-editing siblings, but the usage context is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.