kinocut

Overview Schema Source Related Servers Discussions Admin

glitch_vhs_tracking

Apply a VHS tracking-error glitch effect to video by simulating tape tracking problems with color bleed, rolling bands, and analog noise.

Instructions

Apply VHS tracking error glitch effect.

Simulates VHS tape tracking problems with color bleed, rolling bands, and analog noise.

Args: input_path: Absolute path to input video. output_path: Absolute path for output video. tracking: Tracking error intensity (0-1). Default 0.5. noise_amount: VHS noise intensity (0-1). Default 0.03. color_bleed: Red channel shift in pixels. Default 3. roll_speed: Vertical roll speed. Default 2.

Returns: Dict with success status and output_path.

Input Schema

Name	Required	Description
`tracking`	No
`overwrite`	No	Explicitly allow replacing existing media. Existing non-media files are protected.
`input_path`	Yes
`roll_speed`	No
`color_bleed`	No
`output_path`	No
`noise_amount`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.16.4Oct 24, 2026

addedInput schema / properties / overwrite

Added value: +{
+  "default": false,
+  "description": "Explicitly allow replacing existing media. Existing non-media files are protected.",
+  "title": "Overwrite",
+  "type": "boolean"
+}

Changed1 schema field changedv1.16.0Oct 3, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
Addedv1.5.1Jun 4, 2026

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 full burden. It discloses the visual behavior of the effect and describes the return shape, but omits whether it re-encodes or destroys the source, codec/format constraints, or how it handles an existing output file (the overwrite flag lives only in 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?

Front-loaded with a one-line purpose, followed by a compact Args block and a brief Returns line. Every line earns its place, with only minor redundancy between the first two sentences.

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?

For a 7-parameter effect tool with an output schema present, the description covers nearly all parameters and the effect semantics. The remaining gaps are the undocumented overwrite behavior and the lack of when-to-use routing among numerous sibling glitch tools.

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 14%, so the description must compensate, and it largely does: it documents tracking (0-1), noise_amount (0-1), color_bleed (pixel shift), roll_speed, input_path, and output_path with meanings and defaults. The gap is overwrite, which the description never mentions even though it gates overwriting existing media.

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 ('Apply') and resource ('VHS tracking error glitch effect') plus a concrete visual breakdown (color bleed, rolling bands, analog noise). An agent can distinguish this from glitch_scanline_jitter or glitch_screen_tearing by the effect described, though it never explicitly names the alternatives it differs from.

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 what the effect looks like but not when to choose it over the many sibling glitch tools (glitch_rgb_shift, transition_glitch, effect_noise). No prerequisites, no exclusions, no guidance on input requirements beyond 'absolute path'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server