Skip to main content
Glama
KyaniteLabs

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

video_split_screen

Combines two videos side by side or top to bottom into one split-screen output, letting you compare or present clips together.

Instructions

Place two videos side by side or top/bottom.

Args: left_path: Absolute path to the first video. right_path: Absolute path to the second video. layout: Layout type (side-by-side or top-bottom). output_path: Where to save the output. Auto-generated if omitted.

Input Schema

NameRequiredDescriptionDefault
layoutNoside-by-side
left_pathYes
overwriteNoExplicitly allow replacing existing media. Existing non-media files are protected.
right_pathYes
output_pathNo

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?

With no annotations, the description carries the full behavioral burden but only discloses that output_path is auto-generated when omitted. It says nothing about what happens when the target already exists, how audio tracks from the two inputs are combined, or what resolution/codec is inferred. The destructive nature of writing a new media file is never surfaced in the description.

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 action is front-loaded in the first sentence and the arg list is terse with no filler. Slightly more text than strictly necessary given the schema already covers overwrite, but nothing is wasted.

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?

Output schema exists, so return values need no explanation, and the core parameters are covered. Gaps remain for a no-annotation file-writing tool: overwrite semantics, audio handling, and file-overwrite safety are absent from the description, leaving an agent to discover them from the schema alone.

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 coverage is only 20% (only overwrite is documented in-schema), but the description compensates by explaining left_path/right_path as absolute video paths, output_path as auto-generated if omitted, and — critically — enumerating layout values 'side-by-side or top-bottom' that the schema does not constrain with an enum. Only overwrite is left to the schema, where it is already described.

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: place two videos side by side or top/bottom, with named paths. An agent understands the operation immediately. It does not, however, distinguish itself from layout siblings like video_layout_grid, video_layout_pip, or video_composite_layers, which overlap in purpose.

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 statement of when to choose this over the many other multi-video layout tools (video_layout_grid, video_layout_pip, video_overlay, video_composite_layers). Usage is only inferable from the one-line summary; no exclusions or prerequisites are given.

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