Skip to main content
Glama
KyaniteLabs

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

video_fix_design_issues

Automatically fixes design issues in a video by correcting brightness, contrast, saturation, and audio levels.

Instructions

Auto-fix design issues in a video.

Applies automatic fixes for brightness, contrast, saturation, and audio level issues.

Args: input_path: Absolute path to input video output_path: Absolute path for output (auto-generated if omitted)

Input Schema

NameRequiredDescriptionDefault
overwriteNoExplicitly allow replacing existing media. Existing non-media files are protected.
input_pathYes
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

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It says 'auto-fix' but does not disclose that fixing implies re-encoding/writing a new media file, whether the input is ever modified, what happens to non-media files, or that an explicit overwrite flag is required to replace existing media. Only the output_path auto-generation behavior is disclosed, which is useful but thin for an unannotated mutation 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 with the action and the affected dimensions in two short sentences, followed by a compact args block. Slight redundancy between the title line and the 'Applies automatic fixes' sentence, but no filler.

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?

Return values are covered by the output schema, so their absence is fine. What's missing for a mutation tool with zero annotations is the safety/behavior story (overwrite semantics, input preservation) and any routing guidance among the many sibling video-fix/grade tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33%, and the description compensates partially: it clarifies that input_path and output_path are absolute paths and that output_path is auto-generated when omitted — meaning beyond the bare schema for those two. It does not cover the overwrite parameter at all, but the schema does describe it, so the gap is not fatal.

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+resource ('Auto-fix design issues in a video') and enumerates the dimensions fixed (brightness, contrast, saturation, audio level). However, it never distinguishes this from close siblings like video_design_quality_check (which presumably finds the same issues) or video_ai_color_grade.

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 when-to-use guidance, no stated prerequisites, and no mention of the obvious alternative workflow (run video_design_quality_check first, then this). The agent must infer that this is the remediation counterpart to the QC tool from the name alone.

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