Skip to main content
Glama
KyaniteLabs

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

video_template_preview

Preview a video template's operations, estimated duration, resolution, and file size before rendering, so you can validate settings without processing any video.

Instructions

Preview what a video template would do before rendering.

Analyzes the template and returns a list of operations, estimated output duration, resolution, and file size — without actually processing any video.

Args: template: Template name (tiktok, youtube-shorts, instagram-reel, youtube, instagram-post). input_path: Absolute path to the input video (optional; used for duration probing). duration: Override the estimated duration in seconds. caption: Caption text for TikTok / Instagram Reel / Instagram Post templates. title: Title text for YouTube Shorts / YouTube video templates. music_path: Absolute path to background music file. outro_path: Absolute path to outro video file (YouTube template only).

Input Schema

NameRequiredDescriptionDefault
titleNo
captionNo
durationNo
templateYes
overwriteNoExplicitly allow replacing existing media. Existing non-media files are protected.
input_pathNo
music_pathNo
outro_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

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden well: it says the tool returns a list of operations, estimated output duration, resolution, and file size without actually processing any video. This clearly communicates its non-destructive, analytical behavior, though it does not discuss permissions or side effects such as the overwrite parameter's relevance.

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 description is front-loaded with a clear one-sentence purpose and then a structured Args block. It is appropriately sized, though the Args block partially repeats schema fields and could be slightly tighter.

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?

An output schema exists, so return values need not be explained. The description covers the tool's analysis behavior and most parameters, making it complete enough for correct invocation, with overwrite as the notable omission.

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 13%, so the description meaningfully compensates by explaining template, input_path, duration, caption, title, music_path, and outro_path semantics, including template-specific applicability. It omits the overwrite parameter entirely, leaving one parameter undocumented in the description, but overall adds substantial meaning beyond the schema.

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 states a specific verb and resource: previewing what a video template would do, explicitly before rendering. It distinguishes itself from rendering siblings by saying it analyzes without processing video, though it does not name or contrast adjacent preview tools like video_preview directly.

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?

It implies the tool is used before rendering and describes the scenario as a dry-run analysis. However, it gives no explicit when-not guidance and does not mention alternatives or prerequisites for choosing this preview over other preview/inspection 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