Skip to main content
Glama
KyaniteLabs

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

video_generate_subtitles

Generate SRT subtitles from timed text entries and optionally burn them into a video.

Instructions

Generate SRT subtitles from text entries and optionally burn into video.

Args: entries: List of subtitle entries with keys: start (float), end (float), text (str). input_path: Absolute path to the input video. burn: If True, burn subtitles into the video (default False).

Input Schema

NameRequiredDescriptionDefault
burnNo
entriesYes
overwriteNoExplicitly allow replacing existing media. Existing non-media files are protected.
input_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.2/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. It says subtitles can be burned into the video, implying mutation, but does not explain overwrite behavior, where the SRT is written, or what happens to existing media beyond what the schema's overwrite field already states.

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

Conciseness5/5

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

The description is front-loaded and compact: the first sentence states the core action, and the Args block efficiently documents the important parameters. Every sentence adds useful information without repetition.

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?

Return values are covered by the output schema, and the description documents the complex entries parameter and main options. However, for a mutating media tool with no annotations and low schema coverage, it should also mention overwrite implications and output behavior to be fully complete.

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 25%, but the description compensates well by spelling out entries as a list with start, end, and text keys, and by explaining input_path as an absolute video path and burn as an optional default-false flag. It does not describe overwrite, though the schema itself supplies a description for that parameter.

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: generate SRT subtitles from text entries, optionally burning them into the video. It is clear what the tool does, but it does not distinguish itself from sibling tools such as video_subtitles or video_subtitles_styled.

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?

The description explains the optional burn behavior but gives no guidance on when to use this tool versus alternatives like video_subtitles, video_subtitles_styled, or video_add_text. It also omits prerequisites or when-not-to-use conditions.

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