Skip to main content
Glama
Podcast MCP
by calebn

set_clip_fade_tool

Set fade-in and fade-out durations for a single audio clip, optionally choosing linear, equal-power, or S-curve shapes; fades are clamped to fit the clip.

Instructions

Set the fade-in and fade-out duration of a single clip, and optionally their shapes.

A fade you set is bounded only by the clip: each fade fits in the clip, and fade-out is limited to what fade-in leaves. render.join_fade_max_ms and the episode's Longest automatic join fade (set_join_fade_limit_tool) limit only the fades ShareCut picks by itself. The result reports the applied fade_in_ms / fade_out_ms and clamped. A curve is linear (the default), equal_power or s; left out, the clip keeps its current curve. A curve applies to a fade that is not at a cut or blended join. list_clips_tool names a curve only while it is not linear.

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": {
      "clip_id": "<clip_id>",
      "fade_in_ms": "<fade_in_ms>",
      "fade_out_ms": "<fade_out_ms>"
    },
    "name": "set_clip_fade_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
clip_idYes
fade_in_msYes
fade_out_msYes
project_pathNo
fade_in_curveNo
fade_out_curveNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.4
    • addedInput schema / properties / fade_in_curve
      Added value: +{
      +  "anyOf": [
      +    {
      +      "enum": [
      +        "linear",
      +        "equal_power",
      +        "s"
      +      ],
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Fade In Curve"
      +}
    • addedInput schema / properties / fade_out_curve
      Added value: +{
      +  "anyOf": [
      +    {
      +      "enum": [
      +        "linear",
      +        "equal_power",
      +        "s"
      +      ],
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Fade Out Curve"
      +}
  2. Changed4 schema fields changedv0.1.1
    • addedInput schema / properties / project_path / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / project_path / default
      Added value: +null
    • removedInput schema / properties / project_path / type
      Removed value: -"string"
    • changedInput schema / required
      Previous value: -[
      -  "project_path",
      -  "clip_id",
      -  "fade_in_ms",
      -  "fade_out_ms"
      -]New value: +[
      +  "clip_id",
      +  "fade_in_ms",
      +  "fade_out_ms"
      +]
  3. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does so well: it discloses clamping semantics (each fade fits in the clip, fade-out limited to what fade-in leaves), that the result reports applied fade_in_ms/fade_out_ms plus a 'clamped' flag, and that an omitted curve preserves the clip's current curve. It does not state reversibility, required permissions, or that this is a mutation, but the clamping/limit disclosure is genuinely useful context beyond structured data.

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 purpose is front-loaded in the first sentence, and each subsequent sentence adds distinct operational information (bounds, result fields, curve defaults, list_clips_tool reporting behavior). The wording around the join-fade limits is dense but no sentence is filler.

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?

For a 6-parameter mutation tool with no annotations, the description supplies the missing behavioral and parameter semantics, and an output schema exists so return values need not be restated in detail. The remaining gaps are project_path's purpose and the absence of any note on what happens to adjacent clips or whether the change is undoable.

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 0%, so the description must compensate, and it covers the curve parameters thoroughly: the three curve values (linear default, equal_power, s), the null-default behavior (clip keeps its current curve), and the caveat that a curve applies only to a fade not at a cut or blended join. fade_in_ms/fade_out_ms are explained via the bounding rules, but clip_id and project_path receive no explanation at all.

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 first sentence gives a specific verb and resource: 'Set the fade-in and fade-out duration of a single clip, and optionally their shapes.' The word 'single' implicitly contrasts with a bulk sibling (set_clips_fade_tool), but the description never names that alternative, so the differentiation is left to inference.

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 implied by the scoping details (fades bounded by the clip; automatic join fades are governed by render.join_fade_max_ms and set_join_fade_limit_tool), which help an agent understand this tool's domain. However, there is no explicit when-to-use/when-not statement and no routing to set_clips_fade_tool, apply_fade_recommendations_tool, or fade_joins_tool.

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