Skip to main content
Glama
KyaniteLabs

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

video_batch

Process multiple video files at once by applying the same operation and parameters to each, then save results to an optional output directory.

Instructions

Apply the same operation to multiple video files.

Args: inputs: List of absolute paths to input video files. operation: Operation (trim, resize, convert, filter, blur, color_grade," " watermark, speed, fade, normalize_audio). params: Parameters for the operation. output_dir: Directory for output files. Auto-generated if omitted.

Input Schema

NameRequiredDescriptionDefault
inputsYes
paramsNo
operationYes
overwriteNoExplicitly allow replacing existing media. Existing non-media files are protected.
output_dirNo

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.3/5.0
Behavior2/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 does not say whether outputs can overwrite existing files (the `overwrite` parameter exists in the schema but is never mentioned in the description), what happens if one file in the batch fails, whether the batch is sequential or parallel, or where auto-generated output files land.

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 purpose in one sentence, then a compact Args list where each line carries needed information. The raw docstring formatting ('Args:') is slightly noisy but nothing is padded.

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?

An output schema exists so return values need no explanation, but for a 5-param mutation tool with zero annotations the description should at minimum explain `overwrite`, where auto-generated outputs go, and batch failure semantics. Two of those three gaps remain.

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 20% (only `overwrite` is documented in the schema), and the description compensates by documenting inputs, output_dir, and crucially supplying the allowed `operation` values even though the schema has no enum. The weak spot is `params`, described only as 'Parameters for the operation' with no key structure, and `overwrite` is omitted entirely.

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: applies one operation to many video files, and the enumerated operation list makes the batch counterpart to the single-file siblings (video_trim, video_resize, video_convert, video_filter...) obvious. It never names a sibling explicitly, so it falls short of 5, but an agent can tell it apart from the single-op tools.

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

Usage Guidelines3/5

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

The batch nature implies when to use it (many files, one op), and the operation list hints that per-file tools exist, but there is no explicit when/when-not guidance, no statement about failure behavior or whether to prefer it over looping the single-op tools. Usage is left to inference.

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