Skip to main content
Glama
ffmpeg-mcp

ffmpeg-mcp

by yambal

convert_audio

Converts an audio file from one format to another using FFmpeg, with optional settings for codec, bitrate, sample rate, and channels.

Instructions

Convert audio file to a different format

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_path": "<input_path>",
      "output_path": "<output_path>"
    },
    "name": "convert_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
bitrateNoAudio bitrate (e.g., 128k, 192k, 320k)
channelsNoNumber of audio channels (1 for mono, 2 for stereo)
input_pathYesPath to the input audio file
audio_codecNoAudio codec (e.g., mp3, aac, flac, pcm_s16le)
output_pathYesPath for the output audio file
sample_rateNoSample rate in Hz (e.g., 44100, 48000)

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?

With no annotations, the description carries the full behavioral burden and falls short: it does not say whether an existing output file is overwritten, whether the format is inferred from output_path or must be set via audio_codec, or whether the operation re-encodes lossily. These are exactly the details an agent needs before invoking a file-writing operation.

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 front-loaded sentence with zero padding. It is appropriately terse, though the terseness borders on under-specification for a six-parameter file-producing tool.

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?

For a tool that writes a file with six parameters and no annotations or output schema, the description omits the key behavioral facts: format inference, overwrite behavior, and error conditions. The rich schema covers inputs, but the operational context is incomplete.

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%, with each of the six parameters including an inline description and examples, so the schema already does the explanatory work. The description adds nothing beyond it, which puts it at the baseline rather than above.

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 and resource ('Convert audio file to a different format'), making the operation unmistakable. It does not, however, distinguish itself from siblings like extract_audio, merge_audio, or trim_audio, so an agent must infer the boundary itself.

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 guidance on when to use this versus the sibling audio tools, and no mention of prerequisites such as whether the output format is derived from the output_path extension. The agent gets a purpose but no routing logic.

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