Skip to main content
Glama
KyaniteLabs

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

video_subtitles

Burns SRT, VTT, or ASS subtitles directly into a video, with optional style overrides to control font, color, and positioning in the final rendered output.

Instructions

Burn subtitles (SRT/VTT/authored ASS) into a video.

Args: input_path: Absolute path to the input video. subtitle_path: Absolute path to the subtitle file (.srt, .vtt, or .ass). output_path: Where to save the output. Auto-generated if omitted. style: Optional force_style override applied to any subtitle format including authored ASS (e.g. "FontSize=24,PrimaryColour=&H00FFFFFF"). Omit to preserve an authored ASS file's own styling/positioning.

Input Schema

NameRequiredDescriptionDefault
styleNo
overwriteNoExplicitly allow replacing existing media. Existing non-media files are protected.
input_pathYes
output_pathNo
subtitle_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. Changed2 schema fields changedv1.16.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / style
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Style"
+}
  3. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It usefully discloses that style is a force_style override applying to any format including authored ASS, and that omitting it preserves the ASS file's own styling/positioning. It does not discuss file replacement behavior, permissions, or failure modes; overwrite is only covered by the schema.

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?

Docstring-style Args block, front-loaded purpose statement followed by per-parameter notes. Appropriately sized with no filler, though the Args formatting is slightly redundant with the schema.

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?

Output schema exists, so return values need not be described, and the core parameters are explained. Missing is any statement of how it relates to sibling subtitle tools and any mention of overwrite/safety in the prose, which leaves a small gap for a 5-parameter mutation tool with no annotations.

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 20%, so the description must compensate and largely does: input_path, subtitle_path, output_path (auto-generated if omitted) and style are all explained, with style getting real semantic depth (force_style syntax, ASS preservation behavior). Only overwrite is left to the schema, which does document 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 (burn) and resource (subtitles into a video) with the supported formats enumerated. An agent can tell it is a subtitle-burn operation, but the description never distinguishes it from close siblings like video_subtitles_styled or video_generate_subtitles.

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?

No explicit when-to-use or when-not guidance, and no alternatives named despite several overlapping siblings. The only conditional guidance is about the style parameter (omit to preserve authored ASS styling), which is parameter-level rather than tool-selection guidance.

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