Skip to main content
Glama
KyaniteLabs

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

video_design_quality_check

Analyze a video for layout, typography, color, motion, and composition quality, then automatically fix detected issues when enabled.

Instructions

Run comprehensive design quality analysis on a video.

Checks layout, typography, color, motion, and composition quality. Can automatically fix issues where possible.

Args: input_path: Absolute path to video file auto_fix: If True, automatically apply fixes strict: If True, treat warnings as errors

Input Schema

NameRequiredDescriptionDefault
strictNo
auto_fixNo
overwriteNoExplicitly allow replacing existing media. Existing non-media files are protected.
input_pathYes

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

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

There are no annotations, and the description leaves important behavioral details unstated: whether auto_fix modifies the input file, how overwrite interacts with auto_fix, and what side effects or reversibility constraints apply. It does disclose that fixes are applied automatically and that strict treats warnings as errors, but for a potentially mutating tool this is incomplete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the main purpose, then briefly lists the quality dimensions and fix capability, followed by compact argument explanations. Every sentence adds useful information without unnecessary repetition.

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?

The tool has an output schema, so return values need not be described, and the description covers the main checks and three parameters. However, for a tool with auto-fix behavior and no annotations, it should say more about safety, overwrite behavior, and when this tool is preferable to related quality/fix siblings.

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 25%, so the description appropriately compensates by documenting input_path as an absolute path, auto_fix as applying fixes, and strict as treating warnings as errors. It omits overwrite, but the schema itself describes overwrite, so overall parameter meaning is well covered.

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 action and resource: design quality analysis on a video, with checks for layout, typography, color, motion, and composition. It is clear enough to distinguish from generic quality tools, but it does not explicitly differentiate itself from siblings such as video_quality_check or video_fix_design_issues.

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 tool checks but gives no explicit guidance on when to use it versus alternatives. It mentions auto-fixing capability but does not say when to use this tool instead of video_fix_design_issues or when auto_fix should be avoided.

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