Skip to main content
Glama
KyaniteLabs

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

video_overlay

Overlay a video onto another as picture-in-picture, with control over position, size, opacity, start time, and duration before saving the combined result.

Instructions

Picture-in-picture: overlay a video on top of another.

Args: background_path: Absolute path to the background video. overlay_path: Absolute path to the overlay video. position: Position on screen. Named (top-left, etc.), pixel" " {"x": 100, "y": 50}, or percentage {"x_pct": 0.5, "y_pct": 0.5}. width: Width to scale the overlay to (pixels). height: Height to scale the overlay to (pixels). opacity: Overlay opacity (0.0 to 1.0). start_time: When the overlay appears (seconds). duration: How long the overlay is visible (seconds). output_path: Where to save the output. Auto-generated if omitted. crf: Override CRF value (0-51, lower = better quality). Default 23. preset: Override FFmpeg encoding preset (ultrafast, fast, medium, slow, veryslow).

Input Schema

NameRequiredDescriptionDefault
crfNo
widthNo
heightNo
presetNo
opacityNo
durationNo
positionNotop-right
overwriteNoExplicitly allow replacing existing media. Existing non-media files are protected.
start_timeNo
output_pathNo
overlay_pathYes
background_pathYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.16.4
    • addedInput schema / properties / overwrite
      Added value: +{
+  "default": false,
+  "description": "Explicitly allow replacing existing media. Existing non-media files are protected.",
+  "title": "Overwrite",
+  "type": "boolean"
+}
  2. Changed1 schema field changedv1.16.0
    • addedInput schema / additionalProperties
      Added value: +false
  3. Addedv1.5.1

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description must carry behavioral disclosure. It gives useful defaults and formats, but it omits overwrite behavior, what happens when output exists, permission requirements, side effects, and error conditions for a media-writing operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose sentence is front-loaded and the argument list is efficiently organized. The length is justified by the 12 parameters, though the docstring-style list could be slightly more structured for rapid scanning.

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?

The description covers purpose and most parameter semantics, and an output schema exists so return values need not be explained. However, for a media-writing tool with no annotations, it lacks behavioral and usage context that would make the definition fully self-sufficient.

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

Parameters4/5

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

Schema description coverage is only 8%, so the description must compensate. It does so well by explaining most parameters, including position formats, opacity range, timing semantics, output auto-generation, CRF, and preset choices; only overwrite is not described here, though the schema itself documents it.

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 clearly states a specific action and resource: overlay one video on top of another as picture-in-picture. It is understandable without opening the schema, but it does not distinguish this from adjacent siblings such as video_layout_pip or video_composite_layers.

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?

There is no explicit when-to-use or when-not-to-use guidance. The picture-in-picture phrasing implies a scenario, but it does not mention prerequisites, alternatives, or selection criteria despite many nearby video compositing tools.

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