Skip to main content
Glama

upload_extend_audio

Extend any uploaded audio file with AI-generated content. Provide the audio URL to add new segments using styles and prompts.

Instructions

NEW — Extend uploaded audio (NOT a Suno track) with new AI-generated content. For Suno tracks, use extend_music instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
waitNoSet false to submit and return immediately with the task_id (async mode) — then poll with check_task and fetch with download_result. Recommended for long generations to avoid client-side watchdog timeouts.
modelNoV5
styleNoStyle tags for the extension
titleNo
promptNoDescription of the extension content
filenameNo
uploadUrlYesURL of the audio file to extend
continueAtNoTimestamp in seconds where to start the extension
download_dirNoAbsolute directory to save the file(s) into (created if missing). Defaults to the server's kie/assets/raw/. Must be absolute — the MCP server's working directory is not the caller's.
instrumentalNo
max_wait_secondsNoOverride the blocking-mode polling budget in seconds (default: audio 300). Ignored when wait=false.
Behavior3/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It mentions that the tool generates AI content and hints at async vs sync behavior via the wait parameter, but does not explain potential side effects, authentication needs, or what 'extend' entails precisely. Basic transparency is present but could be richer.

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 two sentences long with no wasted words. It front-loads the core purpose and the key exclusion (Suno tracks), making it highly efficient and scannable.

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?

Given the tool has 11 parameters and no output schema, the description provides the essential purpose and a key sibling distinction but lacks guidance on how to use parameters like continueAt, style, or prompt effectively. It is minimally complete for a complex tool.

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 coverage is 64%, which is moderate. The description itself does not elaborate on parameters beyond what the schema provides. However, the schema descriptions for parameters are already quite informative (e.g., wait with detailed async explanation). The description adds minimal extra meaning, so it meets the baseline but does not exceed it.

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 uploaded audio files (not Suno tracks) with new AI-generated content, using a specific verb and resource. It explicitly distinguishes the tool from extend_music, making its purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly tells when not to use the tool (for Suno tracks) and directs to extend_music as the alternative. This provides clear usage guidance and context for selection among siblings.

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/elibarnett/kie-mcp'

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