Skip to main content
Glama
KyaniteLabs

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

video_storyboard

Extract key frames from a video and assemble them into a storyboard grid for human review. Set frame count and output directory to create review-ready visual summaries.

Instructions

Extract key frames and create a storyboard grid for human review.

Args: input_path: Absolute path to the input video. output_dir: Directory to save frames. Auto-generated if omitted. frame_count: Number of key frames to extract.

Input Schema

NameRequiredDescriptionDefault
overwriteNoExplicitly allow replacing existing media. Existing non-media files are protected.
input_pathYes
output_dirNo
frame_countNo

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. First observedv0.2.0

TDQS

B3.3/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 burden. It never says the tool writes files to disk, how the grid is laid out, what happens if output_dir already contains files, or how the 'overwrite' parameter gates replacement — the schema's overwrite field hints at a destructive overwrite path that the description ignores entirely.

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?

One-line purpose followed by a tight Args list — front-loaded and free of filler. It could be marginally improved by noting the default frame count (8), 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?

An output schema exists, so return-value explanation is correctly omitted. But for a filesystem-mutating tool with no annotations and an unspecified overwrite semantic, the description should state what gets created and how existing output is handled before an agent calls it.

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 25%, and the description meaningfully compensates: it tells the caller input_path must be an absolute path, that output_dir is auto-generated when omitted, and what frame_count controls. Only 'overwrite' is left unaddressed in prose (its schema description partially covers 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?

States a specific verb+resource: extracts key frames and assembles them into a storyboard grid for human review. This is meaningfully more specific than siblings like video_export_frames or video_extract_frame, though it never names those alternatives, so an agent must infer the distinction.

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?

The phrase 'for human review' implies the use case (visual previsualization/approval), but there is no explicit when-to-use vs when-not, no mention of when to prefer video_extract_frame/video_export_frames instead, and no prerequisites stated.

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