Skip to main content
Glama
KyaniteLabs

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

video_ai_color_grade

Apply a color grade to a video using a LUT file, style preset, or reference video to match its color balance.

Instructions

Apply a color grade to a video — by LUT file, style preset, or reference video.

Args: input_path: Video file to grade. output_path: Where to write the graded video. reference_path: Optional reference video — when given, the video's color balance is adjusted to match the reference (overrides style). style: Style preset. One of: auto (gentle contrast lift), warm, cool, vintage, cinematic, dramatic, noir (high contrast, desaturated). lut_path: Optional .cube/.3dl LUT file applied with FFmpeg lut3d — overrides both reference and style for professional grading looks.

Input Schema

NameRequiredDescriptionDefault
styleNoauto
lut_pathNo
overwriteNoExplicitly allow replacing existing media. Existing non-media files are protected.
input_pathYes
output_pathYes
reference_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. Changed1 schema field changedv1.6.0
    • addedInput schema / properties / lut_path
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Lut Path"
+}
  4. Addedv1.5.1

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description bears the full disclosure burden. It reveals the underlying mechanism (FFmpeg lut3d) and the override precedence, but says nothing about whether audio is preserved, re-encode quality, runtime, or supported input codecs. The 'overwrite' safety behavior is only visible in the schema, not surfaced here for a clearly mutating file-writing tool.

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 one-line summary followed by a per-argument breakdown; each arg line adds information rather than restating the name. Mildly verbose in places ('Optional' repeated with re-explanation of override behavior already implied), keeping it short of 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 needn't be explained, and the argument docs plus precedence rules cover everything needed to invoke correctly. For a color-grade transform, the remaining unknowns (audio passthrough, codec) are secondary to correct parameter choice.

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?

With only 17% schema coverage, the description carries the load and largely does: it defines input_path, output_path, reference_path, lut_path (including accepted extensions .cube/.3dl) and enumerates every style value with a semantic gloss (e.g. noir = high contrast, desaturated). The only uncovered parameter is 'overwrite', which is handled by a schema description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource ('Apply a color grade to a video') and immediately enumerates the three mechanisms (LUT file, style preset, reference video). That framing separates it from generic siblings like video_filter and from image-side still_grade, so an agent can identify it without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states an explicit precedence chain: lut_path 'overrides both reference and style', reference_path 'overrides style'. That is real routing guidance an agent would otherwise get wrong. It stops short of naming alternatives (video_filter, still_grade), so no when-not-to-use 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