Skip to main content
Glama
KyaniteLabs

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

video_info_detailed

Extract detailed video metadata including scene changes and dominant colors to analyze content structure and visual composition.

Instructions

Get extended video metadata.

Returns detailed video information including scene change detection and dominant colors.

Args: input_path: Absolute path to input video.

Returns: Dict with duration, fps, resolution, bitrate, has_audio, scene_changes.

Input Schema

NameRequiredDescriptionDefault
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

C2.9/5.0
Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden. It discloses the returned fields but says nothing about read-only safety, computational cost (scene-change detection implies decoding), failure behavior on bad paths, or how the 'overwrite' flag relates to an ostensibly read-only inspection op.

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 opening sentence is front-loaded and the body is short with no filler. The 'Args:' / 'Returns:' blocks partially duplicate the input schema and output schema, which is mild redundancy, but nothing is bloated.

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 the return description is a bonus rather than a requirement, and the input_path semantics are covered. The gaps that matter are the unaddressed 'overwrite' parameter and the missing disambiguation from video_info in a very crowded metadata/inspection tool family.

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 50%. The description adds real value for input_path by specifying it must be an absolute path — information the schema lacks. However, the second parameter 'overwrite' is not mentioned anywhere in the description, which is conspicuous for a metadata read tool.

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 and resource ('Get extended video metadata') and enumerates the distinguishing payload (scene change detection, dominant colors). It does not explicitly name and contrast with the sibling video_info, so the 'detailed vs basic' split is inferred from the word 'extended' rather than stated.

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?

There is no when-to-use guidance, no prerequisite, and no exclusion. The obvious alternative — video_info — is never mentioned, and neither are video_detect_scenes or video_read_metadata, which overlap with the advertised outputs, leaving the agent to guess which metadata tool to call.

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