Skip to main content
Glama
ffmpeg-mcp

ffmpeg-mcp

by yambal

extract_audio

Extract the audio track from a video file and save it as a separate audio file, with optional control over the output codec and bitrate for format conversion needs.

Instructions

Extract audio track from a video file

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": "extract_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
bitrateNoAudio bitrate (e.g., 192k, 320k)
input_pathYesPath to the input video file
audio_codecNoAudio codec (e.g., mp3, aac, pcm_s16le). If not specified, determined by output extension
output_pathYesPath for the output audio file (e.g., output.mp3, output.wav)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden, yet it discloses nothing beyond the core action. It does not say whether an existing output file is overwritten, whether parent directories are created, what happens on a video with no audio stream, or what errors surface.

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 efficient sentence with the action front-loaded and zero filler. It is not padded, though it is terse enough that the brevity comes at the cost of the guidance captured in other dimensions.

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 file-in/file-out operation whose parameters are fully documented in the schema, the description is minimally sufficient. With no annotations and no output schema, however, the agent is left to guess at overwrite semantics and failure modes.

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%, so all four parameters (including bitrate and audio_codec examples) are already documented in the schema. The description adds no meaning beyond that, which is the baseline case.

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+resource pair ('Extract audio track') and names the source domain ('from a video file'), so the operation is unambiguous. It does not, however, distinguish itself from siblings like convert_audio or merge_audio, which an agent may confuse when the input is already an audio file.

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?

Usage is only implied: the phrase 'from a video file' suggests this is the tool for pulling audio out of video containers, while convert_audio presumably handles audio-to-audio. There is no explicit when-to-use, when-not-to-use, or named alternative.

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