Skip to main content
Glama
Ashutos1997

ffmpeg-mcp-server

by Ashutos1997
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

reformat_aspect_ratio

Change a video's aspect ratio to 9:16, 1:1, or 4:5 using blurred borders, solid padding, or center cropping.

Instructions

Change video aspect ratio to 9:16 vertical, 1:1 square, or 4:5 portrait. Adds blurred video borders, solid padding, or center crops.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoFormat mode: 'blur_background' adds blurred video borders, 'fit_pad' adds solid color padding, and 'crop_center' zooms and crops the center. Default: 'blur_background'.blur_background
padColorNoBackground color for fit_pad mode, such as 'black', 'white', or hex '0x1e1e2e'. Default: 'black'.black
inputPathYesPath to the source video file.
blurAmountNoBlur strength (5 to 50) for blur_background mode. Default: 20.
outputPathYesDestination path for the reformatted video.
targetRatioNoTarget aspect ratio: '9:16' for vertical reels, '1:1' for square, '16:9' for horizontal, or '4:5' for portrait. Default: '9:16'.9:16
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 / blurAmount / description
      Previous value: -"Blur intensity (5-50) for 'blur_background' mode. Default: 20"New value: +"Blur strength (5 to 50) for blur_background mode. Default: 20."
    • changedInput schema / properties / hardwareAcceleration / description
      Previous value: -"Whether to 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 source video file"New value: +"Path to the source video file."
    • changedInput schema / properties / mode / description
      Previous value: -"Reformatting mode. 'blur_background' adds an aesthetic blurred background of the video itself. 'fit_pad' adds solid colored padding. 'crop_center' zooms and crops the center."New value: +"Format mode: 'blur_background' adds blurred video borders, 'fit_pad' adds solid color padding, and 'crop_center' zooms and crops the center. Default: 'blur_background'."
    • changedInput schema / properties / outputPath / description
      Previous value: -"Destination path for the reformatted video"New value: +"Destination path for the reformatted video."
    • changedInput schema / properties / padColor / description
      Previous value: -"Background color when using 'fit_pad' mode (e.g. 'black', 'white', or hex '0x1e1e2e')"New value: +"Background color for fit_pad mode, such as 'black', 'white', or hex '0x1e1e2e'. Default: 'black'."
    • changedInput schema / properties / targetRatio / description
      Previous value: -"Target aspect ratio. '9:16' (Reels/Shorts/TikTok), '1:1' (Square), '16:9' (Landscape), '4:5' (Portrait Feed)"New value: +"Target aspect ratio: '9:16' for vertical reels, '1:1' for square, '16:9' for horizontal, or '4:5' for portrait. Default: '9:16'."
  3. Addedv0.3.0

TDQS

B3.1/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. It explains the visual outcome of each mode, which is genuinely useful, but says nothing about whether the output overwrites existing files, encoding cost/quality loss, or failure behavior for invalid paths.

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?

Two tight sentences, front-loaded with the core action and immediately qualifying it with the supported ratios and modes. No filler.

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 7-parameter mutation tool with no annotations and no output schema, the description covers purpose and mode effects but omits usage selection, overwrite semantics, and any error/return expectations.

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 every parameter including enums, defaults, and ranges is already documented in the schema. The description's mention of ratios and border types mirrors what the schema provides rather than adding new semantics.

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 ('Change video aspect ratio') and enumerates the supported ratios and border strategies, which clearly separates it from media_convert or create_split_screen. It stops short of naming a sibling as the alternative.

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?

No guidance on when to pick this over media_convert or concat_media, and no prerequisites such as required input format or that inputPath/outputPath must be supplied. The reader must infer all usage context.

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