Skip to main content
Glama
ffmpeg-mcp

ffmpeg-mcp

by yambal

merge_audio

Combine multiple audio files into a single output file by specifying input paths and a destination path. Use this to consolidate audio tracks for playback or processing.

Instructions

Merge multiple audio files into one

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": {
      "input_paths": "<input_paths>",
      "output_path": "<output_path>"
    },
    "name": "merge_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_pathsYesArray of paths to input audio files
output_pathYesPath for the output merged audio file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/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 and does not meet it. It says nothing about whether output_path is overwritten, what order the files are concatenated in, whether incompatible formats fail or are converted, or how long/sizeable an operation this is.

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?

A single short sentence with no filler and the core action front-loaded. It is arguably under-specified rather than verbose, so it earns credit for efficiency rather than penalization for length.

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 simple two-parameter audio concatenation tool with a complete schema, the definition is minimally sufficient to attempt a call. However, with no annotations and no output schema, the description should have covered the overwrite and ordering behavior the agent cannot get elsewhere.

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 both parameters are already documented as input paths and an output path. The description adds no meaning beyond that, such as ordering semantics for input_paths or overwrite behavior for output_path, so the baseline 3 applies.

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?

States a specific verb (merge) and resource (audio files) and the outcome (one file), so the agent can tell it is a combining operation. It does not differentiate from siblings such as convert_audio or trim_audio, which is the only thing keeping it from 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 Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no mention of alternatives, and no prerequisites (e.g., whether inputs must share codec/sample rate). The agent must infer usage purely from the name and schema.

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