ChatCut

smooth_audio

Idempotent

One-shot polish pass over the ACTIVE timeline's audio: every touching audio cut gets a short centered audio crossfade (builtin:tr-audio-cross-fade, default 4 frames = 2 each side), and every exposed clip edge (gap, timeline start/end, or a silent neighbor) gets a short fade-in/fade-out (default 4 frames). Applies to audio items and video items with audible audio, per track. Use when the user asks to smooth audio, remove pops/clicks at cuts, or "add small crossfades everywhere".

Idempotent and non-destructive — safe to run repeatedly:

Seams that already have an audio transition, and edges that already have a fade, are left untouched.
Locked, muted, and hidden tracks, muted clips, and video clips whose asset has no audio track are skipped and reported.
Seams without enough source handle material for a real crossfade fall back to a fade-out/fade-in pair.
Fades are clamped so fade-in + fade-out never exceed a clip's length.

Everything commits as ONE atomic batch; a failure rolls back the whole sweep. Returns counts (crossfades, fadeIns, fadeOuts, fallbackSeams) plus per-reason skip lists with item id prefixes. validateOnly:true returns the plan without committing.

Not for stylistic transitions: for an audible, deliberate crossfade on one specific cut use edit_item with an explicit duration instead.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "smooth_audio"
  }
}

Input Schema

Name	Required	Description
`trackIds`	No	Restrict the sweep to these track ids (full ids). Omit to sweep every track on the active timeline.
`projectId`	No	Project for this call (full ID or unambiguous prefix). Explicit-timeline calls never change the target of later calls; legacy project selection applies otherwise.
`timelineId`	No
`validateOnly`	No	Plan and report without committing any change.
`fadeDurationInFrames`	No	Fade-in/out length in frames at exposed clip edges (default 4). Stored as seconds using the timeline fps.
`crossfadeDurationInFrames`	No	Crossfade length in frames at touching cuts, centered on the cut (default 4 = 2 frames each side). Clamped per seam by available source handles.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedNov 5, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare idempotent=true and destructive=false, but the description earns its keep by specifying the mechanisms: already-transitioned seams and faded edges are left untouched, locked/muted/hidden tracks and silent video are skipped and reported, insufficient handles fall back to a fade-out/fade-in pair, fades are clamped to clip length, and everything commits as one atomic batch that rolls back on failure.

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 core behavior and default values are front-loaded in the opening sentence, with the idempotency mechanics broken into a scannable bullet list. Some details (default frame counts, clamping by source handles) are repeated in the schema, which is minor waste rather than bloat.

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

Completeness5/5

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

With no output schema, the description supplies the return shape (counts for crossfades, fadeIns, fadeOuts, fallbackSeams plus per-reason skip lists with item id prefixes) and the validateOnly dry-run behavior. For a sweep tool with six optional parameters and complex skip logic, nothing an agent needs in order to call it correctly is missing.

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 83%, so the schema already documents trackIds scoping, projectId/timelineId, validateOnly, and both duration parameters with defaults and clamps. The description restates the defaults (4 frames, 2 each side) and the handle-based clamping but adds no new semantics for the id parameters or the validateOnly plan output beyond what the schema states. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('one-shot polish pass over the ACTIVE timeline's audio') and enumerates exactly what it operates on: audio-bearing cuts get a centered crossfade, exposed edges get fades, restricted to audio items and audible video items per track. It also distinguishes itself from sibling `edit_item` in the same paragraph.

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

Usage Guidelines5/5

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

Gives explicit trigger phrases ('smooth audio', 'remove pops/clicks', 'add small crossfades everywhere') and an explicit exclusion: stylistic, deliberate crossfades on one cut should go to `edit_item` with an explicit duration. Both when-to-use and when-not-to-use are covered.

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

All ChatCut tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.