Skip to main content
Glama
flozonn

Mirelo MCP Server

by flozonn

mirelo_extend_audio_submit

Submit an audio extension job to append new audio to an existing clip. Specify audio source, duration, and optional prompts; receive a job ID and URL for polling the result.

Instructions

Extend Audio (audio-only), asynchronous submission: submit an extend-audio job and return its job_id and job_url for later polling.

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).
Behavior2/5

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

No annotations are provided, so the description bears full responsibility. While it states the tool returns a job_id and job_url, it does not disclose potential rate limits, authentication requirements, error behavior, or other important side effects of submitting an async job.

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 a single, clear sentence with no superfluous words. It front-loads the primary purpose and key output information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of an output schema and annotations, the description is too sparse. It does not elaborate on return format details beyond job_id and job_url, nor does it cover error cases or success indicators, leaving the agent with incomplete context for robust usage.

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 100%, so all parameters have descriptions in the schema. The tool description adds no additional parameter details beyond stating the action, meeting the baseline but not exceeding 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 submits an extend-audio job asynchronously and returns job_id and job_url for polling. It specifies 'audio-only', distinguishing it from the with-video siblings.

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 explicitly mentions 'asynchronous submission' and 'for later polling', providing clear context for when to use this tool over synchronous alternatives like mirelo_extend_audio_generate. The sibling tool names further help differentiate usage.

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