Skip to main content
Glama
AbyAbyss

ffmpeg-mcp-video-editor

by AbyAbyss

Overlay media

overlay_media

Overlay an image or video onto another with control over position, size, opacity, fade, and chroma keying for watermarks, picture-in-picture, or green-screen effects.

Instructions

Composite an image or video on top of another — picture-in-picture, watermark, or a chroma-keyed composite.

Position with a named corner or explicit x/y, scale with 'width', and fade it in and out of existence with 'start'/'end'. Set chroma_key to a hex colour to key out a green or blue screen from the overlay before compositing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNoExplicit x in pixels, overriding position.
yNoExplicit y in pixels, overriding position.
endNoNull means to the end of the base clip.
startNo
widthNoScale the overlay to this width.
encodeNo
marginNo
opacityNo
positionNoNamed position, e.g. 'top-right', 'center', 'bottom-left'.top-right
chroma_keyNoKey out this colour from the overlay, e.g. '#00FF00' for a green screen.
input_pathYesPath to the source media file.
output_pathNoDestination file. If omitted, the output is written into the job's workspace directory and its path is returned by job_result.
chroma_blendNo
overlay_pathYesImage or video to composite on top.
chroma_similarityNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
toolYes
job_idYes
statusNoqueued
messageNoJob queued. Poll job_status for progress, then job_result.
Behavior3/5

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

Annotations are minimal (readOnlyHint=false, destructiveHint=false), so the description carries behavioral burden. It explains fade timing and chroma keying, but does not disclose output overwrite behavior or side effects on source files. No contradiction found.

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 sentences, front-loaded with the primary purpose, and the second sentence efficiently summarizes key parameter behaviors. Every clause earns its place with no fluff.

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?

With 15 parameters, rich schema, and an output schema present, the description provides enough context for selection and invocation. It covers the core compositing behaviors but leaves some subtleties (opacity, margin, blend) to the schema, which is reasonable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds significant meaning beyond the schema: 'x/y override position', 'width scales the overlay', 'start/end fade it in and out', and 'chroma_key hex colour'. This compensates for the 60% schema coverage by clarifying relationships between parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function with a specific verb ('composite') and resource ('an image or video on top of another'), and lists concrete use cases (picture-in-picture, watermark, chroma-keyed). This differentiates it from siblings like text_overlay or transform.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description gives clear contexts for use (picture-in-picture, watermark, chroma-key composite), but does not explicitly mention alternative tools or when not to use it. The intended usage is evident, though not exhaustive.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AbyAbyss/ffmpeg-mcp-video-editor'

If you have feedback or need assistance with the MCP directory API, please join our Discord server