Skip to main content
Glama
KyaniteLabs

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

video_hls_segment

Convert a video into HTTP Live Streaming (HLS) format by splitting it into segments and generating a playlist, with optional quality levels and segment duration settings.

Instructions

Segment a video into HLS (HTTP Live Streaming) format.

Args: input_path: Absolute path to the input video. output_dir: Directory to save segments. Auto-generated if omitted. segment_duration: Target segment duration in seconds (default 4). playlist_name: Name of the master playlist file. qualities: List of quality levels (e.g. ["low", "medium", "high"]).

Input Schema

NameRequiredDescriptionDefault
overwriteNoExplicitly allow replacing existing media. Existing non-media files are protected.
qualitiesNo
input_pathYes
output_dirNo
playlist_nameNoplaylist.m3u8
segment_durationNo

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

C2.9/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 the behavioral burden. It does not disclose that the tool writes files to disk, what happens to existing output, or the significance of the overwrite flag. The schema has an overwrite parameter with protection semantics, but the description omits this important behavior.

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 the core action and then uses a compact Args list. It is appropriately sized and mostly free of waste, though the argument list could be slightly more selective or integrated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a file-producing mutation tool with no annotations and a low-coverage schema, the description should explain write behavior and overwrite semantics. It covers most argument meanings but omits the safety-relevant overwrite flag entirely. The presence of an output schema means return values need not be described, but operational safety context is still missing.

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

Parameters3/5

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

Schema description coverage is low at 17%, so the description must compensate. It usefully explains input_path, output_dir, segment_duration, playlist_name, and qualities with an example, which adds meaning beyond the bare schema. However, it completely omits the overwrite parameter, which is behaviorally important for a file-writing tool.

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: 'Segment a video into HLS (HTTP Live Streaming) format.' An agent can understand the core operation. However, it does not differentiate this tool from nearby siblings such as video_export or video_convert, which may also produce HLS or segmented outputs.

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 guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. The description only defines what the tool does and lists arguments, leaving selection context entirely implicit.

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