Skip to main content
Glama
KyaniteLabs

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

video_filter

Apply visual filters such as blur, color presets, brightness, or sharpening to video files, then save the processed result to a chosen or auto-generated output path.

Instructions

Apply a visual filter to a video.

Common presets: - blur: params={"radius": 5, "strength": 1} - color_preset: params={"preset": "warm"} (warm, cool, vintage, cinematic, noir)

Args: input_path: Absolute path to the input video. filter_type: Filter type (blur, sharpen, brightness, contrast, saturation," " grayscale, sepia, invert, vignette, color_preset, denoise," " deinterlace, ken_burns, reverb, compressor, pitch_shift," " noise_reduction). params: Optional filter parameters (e.g. radius for blur, preset for color_preset). output_path: Where to save the output. Auto-generated if omitted. crf: Override CRF value (0-51, lower = better quality). Default 23. preset: Override FFmpeg encoding preset (ultrafast, fast, medium, slow, veryslow).

Input Schema

NameRequiredDescriptionDefault
crfNo
paramsNo
presetNo
overwriteNoExplicitly allow replacing existing media. Existing non-media files are protected.
input_pathYes
filter_typeYes
output_pathNo

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

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

With no annotations, the description must carry the full behavioral burden. It discloses that output_path is auto-generated and exposes CRF/preset encoding controls, but it never states whether the input is preserved, whether audio is kept, supported formats, or the effect of re-encoding. The inclusion of audio filters under a 'visual filter' description also creates a scope inconsistency.

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 and generally organized into presets then Args. The long filter_type enumeration is justified, though the section is somewhat list-heavy and repeats schema content because schema coverage is low.

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?

Given seven parameters, no annotations, and an output schema, the description covers enough to construct a call but not enough to predict behavior confidently. Missing media handling details (formats, audio preservation, overwrite semantics beyond the schema) leave gaps for a mutation tool.

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 14%, so the description must compensate, and it largely does: it names all required parameters, enumerates the allowed filter_type values, gives params examples for blur and color_preset, defines CRF range/default, lists preset values, and explains output_path auto-generation. It omits overwrite, but that parameter is described in the schema, and it does not explain per-filter param requirements for the remaining filters.

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 first sentence states a specific verb and resource ('Apply a visual filter to a video'). It does not distinguish this from overlapping siblings such as effect_vignette, video_ai_color_grade, or the glitch tools, and the later filter list includes audio filters (reverb, compressor, pitch_shift), which slightly muddies the stated 'visual' scope.

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 offers preset examples for filter_type but never states when this tool should be chosen over alternatives like video_convert, video_ai_color_grade, effect_vignette, or video_edit. No prerequisites, exclusions, or sibling routing are provided.

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