Skip to main content
Glama
flozonn

Mirelo MCP Server

by flozonn

mirelo_extend_audio_generate

Appends newly generated audio to an existing audio input and provides the result URL. Use to extend audio clips synchronously.

Instructions

Extend Audio (audio-only), synchronous: append newly generated audio to an existing audio input and return the result URL(s).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
loopNoWhether to loop the appended audio. Defaults to false.
audioYesAudio Input_Source: { "type": "url", "audio_url": <public url> } or { "type": "asset", "asset_id": <asset id> }.
promptNoOptional text prompt conditioning the appended audio (1-5000 characters when provided).
num_samplesNoNumber of samples to generate (integer >= 1). Defaults to 1.
model_versionNoModel version. Extend_Audio supports only "v1.6" (the default).
append_duration_msYesMilliseconds of new audio to append. Required. When loop is false: 1000-30000. When loop is true: at least 2000 (total output duration must be 5000-60000).
Behavior3/5

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

The description states 'synchronous' and 'return the result URL(s)', but no annotations exist to provide safety info. It does not disclose side effects, authentication needs, or rate limits. The transparency is adequate but relies on the schema for details.

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 consists of a single, front-loaded sentence that conveys all key information. There is no unnecessary text, making it highly concise and structured.

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?

For a tool with 6 parameters and no output schema, the description is minimal. It omits details about the return format beyond 'URL(s)' and does not mention that a preflight step may be needed. The schema fills gaps, but the description alone is only moderately 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% for all 6 parameters. The description adds no additional meaning beyond what is documented in the schema, so the baseline score of 3 is appropriate.

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 verb 'Extend Audio' and resource 'existing audio input', explicitly noting it is audio-only and synchronous. It distinguishes from sibling tools like 'mirelo_extend_audio_with_video_generate' by specifying 'audio-only'.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool versus siblings (e.g., preflight or submit variants). The synchronous nature is mentioned, but there is no mention of when to choose this over other tools or any prerequisites.

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/flozonn/mirelo-mcp'

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