Skip to main content
Glama

producer_extend_music

Extend an existing song from a chosen timestamp by adding new sections such as verses, a bridge, or an outro; use it when a generated track is too short.

Instructions

Extend an existing song from a specific timestamp with new content.

This allows you to continue a previously generated song, adding new sections
like additional verses, a bridge, or an outro.

Use this when:
- A generated song is too short and you want to add more
- You want to add a bridge or outro to an existing song
- You're building a longer song piece by piece

Returns:
    Task ID and the extended audio information.

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": {
      "audio_id": "<audio_id>",
      "continue_at": "<continue_at>"
    },
    "name": "producer_extend_music"
  }
}

Input Schema

NameRequiredDescriptionDefault
asyncNoWhether to process the request asynchronously.
lyricNoLyrics for the extended section. Use section markers like [Verse], [Chorus], [Bridge], [Outro]. The extension will continue from where the original song left off.
modelNoModel version to use for the extension.FUZZ-2.0
promptNoPrompt for the extension. Leave empty to maintain the original style, or specify how to change the style mid-song.
audio_idYesID of the audio to extend. This is the 'id' field from a previous generation result.
continue_atYesPositive timestamp in seconds where to start the extension. For example, 120.5 means continue from 2 minutes and 0.5 seconds into the song.
callback_urlNoWebhook callback URL for asynchronous notifications.
instrumentalNoGenerate an instrumental extension. Otherwise lyric is required.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.23
    • changedInput schema / properties / continue_at / description
      Previous value: -"Timestamp in seconds where to start the extension. For example, 120.5 means continue from 2 minutes and 0.5 seconds into the song."New value: +"Positive timestamp in seconds where to start the extension. For example, 120.5 means continue from 2 minutes and 0.5 seconds into the song."
    • addedInput schema / properties / continue_at / exclusiveMinimum
      Added value: +0
    • addedInput schema / properties / instrumental
      Added value: +{
      +  "default": false,
      +  "description": "Generate an instrumental extension. Otherwise lyric is required.",
      +  "title": "Instrumental",
      +  "type": "boolean"
      +}
  2. Changed2 schema fields changedv0.1.18
    • addedInput schema / properties / prompt
      Added value: +{
      +  "default": "",
      +  "description": "Prompt for the extension. Leave empty to maintain the original style, or specify how to change the style mid-song.",
      +  "title": "Prompt",
      +  "type": "string"
      +}
    • removedInput schema / properties / style
      Removed value: -{
      -  "default": "",
      -  "description": "Music style for the extension. Leave empty to maintain the original style, or specify to change the style mid-song.",
      -  "title": "Style",
      -  "type": "string"
      -}
  3. Changed1 schema field changedv0.1.16
    • addedInput schema / properties / async
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Whether to process the request asynchronously.",
      +  "title": "Async"
      +}
  4. Addedv0.1.13
  5. Removedv0.1.12
  6. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses that a task ID is returned and that the extension continues 'from where the original song left off,' which is genuinely useful. It says nothing about async defaults, cost/latency, whether the original audio is preserved or mutated, or what happens when continue_at exceeds the song length.

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 structure is strong: a one-line purpose statement, then a scoped bullet list of use cases, all front-loaded with no preamble. The trailing 'Returns:' section is largely wasted because an output schema already exists.

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?

With an output schema present and 100% parameter coverage, the description only needs to cover behavior and routing. It handles the use-case side well but leaves the async/callback contract and model selection (a whole enum plus a producer_list_models sibling) unexplained. Adequate, not complete.

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 the schema already documents every parameter including continue_at's format, lyric section markers, and model enum. The description adds no parameter-level detail beyond restating the continue-at concept. Baseline 3 applies when the schema does the heavy lifting.

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 first sentence gives a specific verb and resource: 'Extend an existing song from a specific timestamp with new content.' That is clearly distinguishable from siblings like producer_generate_music, producer_cover_music, and producer_variation_music. It stops short of naming the closest alternative, producer_replace_section, so it falls short of a 5.

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' block supplies three concrete scenarios (song too short, adding a bridge/outro, building a longer song piece by piece), which is well above the norm for when-to-use guidance. It omits when-not-to-use and never mentions producer_replace_section, which is the obvious alternative when the goal is to change an existing section rather than append new material.

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