Skip to main content
Glama
KyaniteLabs

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

video_text_animated

Overlay animated text on video with fade, slide-up, or typewriter effects. Set text, font, color, position, start time, and duration to caption or label clips.

Instructions

Add animated text to video.

Overlay text with animation effects (fade, slide, etc.).

Args: input_path: Absolute path to input video. text: Text to display. output_path: Absolute path for output video. animation: Animation type (fade, slide-up, typewriter). Default fade. font: Font family. Default Arial. size: Font size. Default 48. color: Text color. Default white. position: Text position. Default center. start: Start time in seconds. Default 0. duration: Display duration. Default 3.0.

Returns: Dict with success status and output_path.

Input Schema

NameRequiredDescriptionDefault
fontNoArial
sizeNo
textYes
colorNowhite
startNo
durationNo
positionNocenter
animationNofade
overwriteNoExplicitly allow replacing existing media. Existing non-media files are protected.
input_pathYes
output_pathNo
typewriter_speedNo

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.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It mentions the return shape and animation options, but it does not disclose side effects, overwrite behavior, supported formats, or permission requirements for a tool that writes a new video file.

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 definition is front-loaded with the core purpose and then uses a structured Args/Returns layout. It is appropriately sized for a 12-parameter tool, though some defaults duplicate the schema and the Returns section adds little because an output schema exists.

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?

Given the low schema description coverage and absent annotations, the description provides enough parameter semantics for an agent to invoke most capabilities correctly. It misses behavioral safety details and two parameters, but the output schema covers return values and the core invocation path is well documented.

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 8%, so the description must compensate, and it does for most parameters by explaining input_path, text, output_path, animation values, font, size, color, position, start, and duration. It omits overwrite and typewriter_speed, which keeps it from a 5.

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: adding animated text overlays to video. It clearly defines the operation but does not explicitly distinguish it from sibling tools such as video_add_text or video_add_texts, so it falls short of a 5.

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 intended use is implied by 'Add animated text to video' and 'Overlay text with animation effects,' but there is no explicit guidance on when to choose this tool over static text siblings or subtitles, and no exclusions are 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