Skip to main content
Glama

producer_extend_music

Extend a generated song from a given timestamp by adding new sections like verses, bridge, or outro. Provide lyrics and optional style to continue or change the song's direction.

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.

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations provided, the description must carry the behavioral burden. It explains the extension operation and return value (Task ID and audio info), but lacks details on side effects (e.g., whether original is preserved), authentication needs, or rate limits. It is adequate but not comprehensive.

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?

The description is concise and well-structured with a clear first sentence, bullet-point use cases, and a return value line. Every sentence serves a purpose without redundancy.

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?

Given 6 parameters, 100% schema coverage, and an output schema, the description covers core behavior and use cases. Minor gaps remain about whether the extension is appended or inserted at the timestamp, but overall it is sufficient.

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 description adds limited value beyond the schema. It reinforces the purpose of parameters (e.g., 'use section markers like [Verse]') but does not provide significant new information.

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

Purpose5/5

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

The description clearly states the tool extends an existing song from a specific timestamp, with explicit use cases for adding verses, bridges, or outros. It distinguishes itself from sibling tools like producer_generate_music by focusing on continuation of previously generated audio.

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 description provides specific scenarios for use (e.g., song too short, adding sections, building piece by piece). It does not explicitly mention when not to use it or alternatives, but the context is clear enough for selection.

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/AceDataCloud/ProducerMCP'

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