Skip to main content
Glama
Ashutos1997

ffmpeg-mcp-server

by Ashutos1997
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

media_convert

Convert video and audio files between formats with presets for web MP4 (H.264/AAC), WebM, and animated GIF; control resolution, frame rate, quality, and hardware acceleration.

Instructions

Convert video and audio files between formats. Includes presets for web MP4 (H.264/AAC), WebM (VP9/Opus), and animated GIF. Supports hardware acceleration on Apple Silicon, NVIDIA, Intel, and AMD.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
crfNoQuality factor from 0 to 51. Lower numbers mean higher quality. Default: 23 for MP4, 30 for WebM.
fpsNoTarget frame rate in frames per second, such as 30, 60, or 15
presetNoEncoding preset: 'web_mp4' for browser playback, 'webm' for WebM video, 'gif' for animated GIF, or 'auto'. Default: 'auto'.
inputPathYesPath to the source media file to convert
outputPathYesDestination path for the converted file (e.g. ./output.mp4, ./output.webm, ./animation.gif)
resolutionNoTarget size formatted as 'WIDTHxHEIGHT', such as '1920x1080' or '1280x720'
hardwareAccelerationNoUse hardware-accelerated video encoding (VideoToolbox, NVENC, QSV, etc.) when available. Default: true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • changedInput schema / properties / hardwareAcceleration / description
      Previous value: -"Use Apple Silicon VideoToolbox encoding when available. Default: true."New value: +"Use hardware-accelerated video encoding (VideoToolbox, NVENC, QSV, etc.) when available. Default: true."
  2. Changed7 schema fields changedv0.4.2
    • changedInput schema / properties / crf / description
      Previous value: -"Constant Rate Factor quality (0-51). Lower is higher quality. Default: 23 for H.264, 30 for VP9."New value: +"Quality factor from 0 to 51. Lower numbers mean higher quality. Default: 23 for MP4, 30 for WebM."
    • changedInput schema / properties / fps / description
      Previous value: -"Target frame rate, e.g. 30, 60, or 15 (great for GIFs)"New value: +"Target frame rate in frames per second, such as 30, 60, or 15"
    • changedInput schema / properties / hardwareAcceleration / description
      Previous value: -"Use Apple Silicon VideoToolbox hardware acceleration if available (default: true)"New value: +"Use Apple Silicon VideoToolbox encoding when available. Default: true."
    • changedInput schema / properties / inputPath / description
      Previous value: -"Path to the input media file"New value: +"Path to the source media file to convert"
    • changedInput schema / properties / outputPath / description
      Previous value: -"Destination file path (e.g. ./output.mp4)"New value: +"Destination path for the converted file (e.g. ./output.mp4, ./output.webm, ./animation.gif)"
    • changedInput schema / properties / preset / description
      Previous value: -"Encoding preset. 'web_mp4' ensures universal browser playback (H.264/yuv420p/faststart). 'gif' uses 2-pass palette generation."New value: +"Encoding preset: 'web_mp4' for browser playback, 'webm' for WebM video, 'gif' for animated GIF, or 'auto'. Default: 'auto'."
    • changedInput schema / properties / resolution / description
      Previous value: -"Target resolution, e.g. '1920x1080', '1280x720', '640x360'"New value: +"Target size formatted as 'WIDTHxHEIGHT', such as '1920x1080' or '1280x720'"
  3. Changed1 schema field changedv0.3.0
    • addedInput schema / properties / hardwareAcceleration
      Added value: +{
+  "description": "Use Apple Silicon VideoToolbox hardware acceleration if available (default: true)",
+  "type": "boolean"
+}
  4. First observedv0.1.0

TDQS

A3.5/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 full behavioral burden. It discloses useful capability details such as preset codecs and hardware-accelerated encoding, but it does not explain output-writing behavior, overwrite semantics, failure handling, or what happens when hardware acceleration is unavailable.

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 front-loaded with the core action, then adds preset and hardware details in a compact four-sentence structure. There is no redundant wording, and each sentence contributes useful context.

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 seven-parameter media mutation tool with no annotations and no output schema, the description covers purpose, presets, and hardware acceleration but leaves gaps around return values, overwrite behavior, and error conditions. The schema fills in parameter details, but the description is only partially complete for the tool's complexity.

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 seven parameters thoroughly. The description adds some useful meaning for the preset parameter by naming codecs such as H.264/AAC and VP9/Opus, but it does not enrich the other major parameters like crf, fps, or resolution.

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: convert video and audio files between formats. It also names concrete preset targets, so the tool is easy to identify. It does not explicitly differentiate itself from related siblings such as compress_video or reformat_aspect_ratio.

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 implicitly clear: use this when changing media container/codec formats. However, the description gives no explicit when-to-use guidance, no exclusions, and no comparison to alternatives like compress_video or reformat_aspect_ratio.

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