Skip to main content
Glama
KyaniteLabs

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

video_normalize_audio

Normalize video audio loudness to a target LUFS level using presets for YouTube, broadcast, or streaming platforms.

Instructions

Normalize audio loudness to a target LUFS level.

Common presets: -16 (YouTube), -23 (EBU R128/broadcast), -14 (Apple/Spotify).

Args: input_path: Absolute path to the input video. target_lufs: Target integrated loudness in LUFS (default -16 for YouTube). output_path: Where to save the output. Auto-generated if omitted. lra: Target loudness range in LU. true_peak_dbtp: Maximum true peak in dBTP; omitted uses the engine default. fade_seconds: Boundary fade duration; omitted uses the engine default.

Input Schema

NameRequiredDescriptionDefault
lraNo
overwriteNoExplicitly allow replacing existing media. Existing non-media files are protected.
input_pathYes
output_pathNo
target_lufsNo
fade_secondsNo
true_peak_dbtpNo

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. Changed4 schema fields changedv1.16.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / fade_seconds
      Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Fade Seconds"
+}
    • addedInput schema / properties / lra
      Added value: +{
+  "default": 11,
+  "title": "Lra",
+  "type": "number"
+}
    • addedInput schema / properties / true_peak_dbtp
      Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "True Peak Dbtp"
+}
  3. Addedv1.5.1

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It says the output path is auto-generated when omitted and that some values use engine defaults, but it does not state whether the input is preserved, how overwrite is handled, whether the video is re-encoded, or what operational constraints apply.

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 core purpose and presets, then presents parameters in a compact argument list. Every sentence adds usable information without repetition or 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?

An output schema exists, so return values need not be explained, and the description does a good job documenting most parameters despite low schema coverage. However, for a media mutation tool with no annotations, it still lacks enough context about safety, overwrite behavior, and relationship to sibling audio tools to be fully self-sufficient.

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 low at 14%, and the description compensates by explaining six of seven parameters, including absolute input path, LUFS presets, auto-generated output path, loudness range units, true peak units, and fade duration defaults. It omits the overwrite parameter, though that parameter has its own schema description.

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 clearly states a specific verb and resource: normalizing audio loudness to a target LUFS level, with common platform presets that clarify the domain. It does not differentiate this tool from nearby audio siblings such as sound_qa_loudness, sound_master_render, or video_mix_audio, so sibling selection still requires inference.

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 gives target LUFS presets for YouTube, broadcast, and streaming, but those guide parameter choice rather than when to choose this tool over alternatives. It contains no explicit when-to-use, when-not-to-use, or alternative-tool 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