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

ffmpeg-mcp-server

by Ashutos1997
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_split_screen

Combine two video files into a vertical (Reels/TikTok) or horizontal split-screen layout. Mix audio tracks from both clips and embed subtitles into your final video output.

Instructions

Combine two video files into a split-screen video. Stacks clips vertically (1080x1920 for Reels and TikTok) or places them side-by-side. Supports audio mixing and subtitle embedding.

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": {
      "firstVideoPath": "<firstVideoPath>",
      "secondVideoPath": "<secondVideoPath>",
      "outputPath": "<outputPath>"
    },
    "name": "create_split_screen"
  }
}

Input Schema

NameRequiredDescriptionDefault
layoutNoSplit layout: 'vertical_9_16' (1080x1920 stacked top/bottom for Reels and TikTok), 'horizontal_16_9' (1920x1080 side-by-side), or 'square_1_1' (1080x1080 stacked). Default: 'vertical_9_16'.vertical_9_16
outputPathYesDestination path for the split-screen output file (e.g. './reel.mp4').
audioSourceNoAudio track selection: 'mix' (blends audio from both videos), 'first' (uses only top/left audio), 'second' (uses only bottom/right audio), or 'mute'. Default: 'mix'.mix
subtitlesPathNoOptional path to an .srt or .vtt subtitle file to embed into the output video.
firstVideoPathYesPath to the top video (vertical layout) or left video (horizontal layout).
secondVideoPathYesPath to the bottom video (vertical layout) or right video (horizontal layout).
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. Addedv0.4.2

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden, yet it omits the operationally important traits: whether an existing file at outputPath is overwritten, how mismatched clip durations or resolutions are handled, and roughly how long/reliably a two-input encode completes. It does disclose the composition model (stacked vs side-by-side, audio mixing, subtitle embedding), which is why it is not a 1.

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 sentences with zero filler: the core action and output framing come first, capability details second. Nothing is repeated and every clause carries information.

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, file-writing tool with no annotations and no output schema, the description is adequate on composition but silent on the return value (does it yield the output path or nothing?), overwrite behavior, and failure modes. An agent could call it correctly but not predict its side effects.

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 coverage is 100% and every parameter, including both enums and their defaults, is already documented in the schema. The description restates the layout and audio behavior in prose but adds no new constraints, formats, or edge cases, so the baseline 3 applies.

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 gives a specific verb and resource — 'Combine two video files into a split-screen video' — plus the spatial arrangement options, which clearly separates it from a plain concat_media call. It never names a sibling or states the boundary explicitly, so an agent must infer the distinction from the tool name alone.

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 via the mention of Reels/TikTok and the layout options; there is no statement of when to pick this over concat_media, add_overlay, or reformat_aspect_ratio, and no prerequisites (e.g., matching durations, codec compatibility) are called out.

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