Skip to main content
Glama

Normalize Loudness

normalize_audio
Destructive

Adjust audio loudness to a delivery target such as YouTube, podcast, or broadcast using two-pass EBU R128, while copying video unchanged and reporting before/after levels.

Instructions

Normalize loudness to a delivery target (two-pass EBU R128 loudnorm); video is copied. Reports loudness before and after.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "input": "<input>"
    },
    "name": "normalize_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesPath to the source video or audio file.
outputNoOptional output path. Defaults under SCREENCAST_HOME/edits.
targetNoyoutube (-14 LUFS, default), podcast (-16), broadcast (-23), or a LUFS number (-70 to -5).
overwriteNoAllow replacing an existing file at the output path (default false).

Output Schema

NameRequiredDescriptionDefault
outputPathYesPath of the file written.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.49.1
    • changedInput schema / properties / target / anyOf
      Previous value: -[
      -  {
      -    "enum": [
      -      "youtube",
      -      "podcast",
      -      "broadcast"
      -    ],
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "youtube",
      +      "podcast",
      +      "broadcast"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "maximum": -5,
      +    "minimum": -70,
      +    "type": "number"
      +  }
      +]
    • changedInput schema / properties / target / description
      Previous value: -"youtube (-14 LUFS, default), podcast (-16), broadcast (-23), or a LUFS number."New value: +"youtube (-14 LUFS, default), podcast (-16), broadcast (-23), or a LUFS number (-70 to -5)."
  2. Changed2 schema fields changedv0.47.0
    • changedInput schema / properties / target / description
      Previous value: -"Loudness target: 'youtube' (-14 LUFS, default), 'podcast' (-16 LUFS), 'broadcast' (EBU R128, -23 LUFS), or a LUFS number such as -18."New value: +"youtube (-14 LUFS, default), podcast (-16), broadcast (-23), or a LUFS number."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "outputPath": {
      +      "description": "Path of the file written.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "outputPath"
      +  ],
      +  "type": "object"
      +}
  3. First observedv0.32.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag it as destructive/non-idempotent, and the description adds non-obvious behavior: video is stream-copied (no video re-encode), the process is two-pass EBU R128, and loudness is reported before and after. It leaves unstated the cost of two passes and that overwrite defaults to off only via the schema, so it is strong but not exhaustive.

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?

Two tight sentences with the action and method front-loaded, followed by the two most decision-relevant facts (video copied, before/after report). No filler or restatement of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A single-purpose tool with full schema coverage and an output schema (so return values need not be explained); the description covers method, side effects, and reporting. Only minor gaps remain around performance expectations and failure modes.

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 description coverage is 100%, so parameter meaning is already carried by the schema (target enum values with LUFS, overwrite default, output default path). The description's 'delivery target' framing adds a little conceptual glue but no syntax or format detail beyond the schema. Baseline 3 applies.

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?

Names a specific verb and resource ('Normalize loudness') plus the standard it applies (two-pass EBU R128 loudnorm), which separates it from sibling audio tools like denoise or compress. It does not name an explicit alternative, so it stops short of a 5.

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?

Usage is only implied: the phrase 'to a delivery target' suggests it is the tool for hitting platform loudness specs, but there is no explicit when-to-use/when-not guidance or pointer to a sibling (e.g., denoise for noise, compress for dynamics).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.