Skip to main content
Glama
Sign In
ffmpeg-mcp-server

ffmpeg-mcp-server

by Ashutos1997
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

extract_audio

Extract an audio track from a video into a standalone audio file, with presets for 16kHz mono WAV speech recognition, MP3, AAC, FLAC, or stream copy.

Instructions

Extract an audio track from a video file into a standalone audio file. Supports the 'whisper_wav' preset (16kHz mono WAV) for speech recognition models, plus MP3, AAC, FLAC, and stream copy.

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": {
      "inputPath": "<inputPath>",
      "outputPath": "<outputPath>"
    },
    "name": "extract_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoAudio format: 'whisper_wav' (16kHz mono WAV for Whisper), 'mp3', 'aac', 'flac', or 'copy' (extract without re-encoding). Default: 'mp3'.
bitrateNoTarget audio bitrate for MP3 or AAC (e.g. '128k', '192k', '320k').
inputPathYesPath to the source video or audio file.
outputPathYesDestination path for the output audio file (e.g. './extracted.wav' or './audio.mp3').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • changedInput schema / properties / format / description
      Previous value: -"Audio format: 'whisper_wav' (16kHz mono WAV for Whisper), 'mp3', 'aac', 'flac', or 'copy' (extract without re-encoding)."New value: +"Audio format: 'whisper_wav' (16kHz mono WAV for Whisper), 'mp3', 'aac', 'flac', or 'copy' (extract without re-encoding). Default: 'mp3'."
  2. Changed4 schema fields changedv0.4.2
    • changedInput schema / properties / bitrate / description
      Previous value: -"Audio bitrate, e.g. '192k', '320k' (for mp3/aac)"New value: +"Target audio bitrate for MP3 or AAC (e.g. '128k', '192k', '320k')."
    • changedInput schema / properties / format / description
      Previous value: -"Audio format preset. 'whisper_wav' generates 16kHz mono PCM. 'copy' extracts audio without re-encoding."New value: +"Audio format: 'whisper_wav' (16kHz mono WAV for Whisper), 'mp3', 'aac', 'flac', or 'copy' (extract without re-encoding)."
    • changedInput schema / properties / inputPath / description
      Previous value: -"Path to the input video file"New value: +"Path to the source video or audio file."
    • changedInput schema / properties / outputPath / description
      Previous value: -"Destination audio file path (e.g. ./audio.mp3, ./audio.wav)"New value: +"Destination path for the output audio file (e.g. './extracted.wav' or './audio.mp3')."
  3. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It usefully discloses that stream copy extracts without re-encoding and that whisper_wav produces 16kHz mono WAV for speech recognition. It does not address overwrite behavior, failure modes when no audio track exists, or file operation semantics, leaving meaningful behavioral gaps.

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 two front-loaded sentences with no wasted wording. The primary action is stated first, followed by concise format support details.

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

Completeness4/5

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

For a moderately complex file-extraction tool with fully described parameters but no annotations or output schema, the description covers purpose and format behavior well. It could be more complete by mentioning return behavior or overwrite semantics, but it provides enough to call the tool correctly.

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 the schema already documents all four parameters thoroughly. The description reinforces the format options and whisper preset, but adds little beyond what the schema already states, so baseline 3 is appropriate.

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?

The description states a specific verb and resource: extract an audio track from a video file into a standalone audio file. It names supported formats including the whisper_wav preset, making the tool's function clear. It does not explicitly distinguish itself from siblings like media_convert or normalize_audio, so it falls short of 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 Guidelines3/5

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

Usage is implied by the extraction scenario and the note that whisper_wav is for speech recognition models. However, there is no explicit guidance on when to use this tool versus media_convert or normalize_audio, and no exclusions or prerequisites are stated.

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

Deploy Server

Other Tools