Skip to main content
Glama
Podcast MCP
by calebn

set_join_fade_limit_tool

Set the maximum automatic join fade length (0-200 ms) for an episode so automatic fades stay under your cap; pass null to restore the app default.

Instructions

Set the episode's Longest automatic join fade in ms (default 40, 0 to 200); null returns to the app default.

This is a limit, not an applied length: ShareCut picks each join's fade itself (fade_joins_tool, Smooth all joins via apply_fade_recommendations_tool, approve-time fades) and never goes above it, so joins can come out shorter (a limit of 120 may give 77 ms). To give joins an exact length use fade_joins_tool with fade_ms (also held to the limit, so raise it first for longer joins). Fades set by hand with set_clip_fade_tool, set_clips_fade_tool or set_clip_join_tool can be longer, and no existing fade changes. Saved in the episode file and undoable; it makes no stem stale. list_clips_tool reports the value in force as join_fade_limit_ms.

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": {
      "ms": "<ms>"
    },
    "name": "set_join_fade_limit_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
msYes
project_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.4

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses that existing fades are unchanged, the value is saved in the episode file, the change is undoable, and no stem becomes stale. It even explains the indirect effect (a limit of 120 may yield 77 ms) and where the effective value is reported (list_clips_tool's join_fade_limit_ms).

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 definition is front-loaded in the first sentence and the limit-versus-length distinction follows immediately. It is dense but every clause carries distinct information; the parenthetical list of internal callers (approve-time fades, Smooth all joins) is slightly heavier than needed.

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?

An output schema exists, so return values need no explanation, and the description covers persistence, undo, and interaction with sibling fade tools thoroughly. The only real gap is the unexplained project_path parameter, which matters for a tool that writes to an episode file.

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; it fully specifies ms (default 40, range 0-200, null restores app default). The second parameter, project_path, is never mentioned, leaving its meaning and default behavior to the bare schema title.

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?

States a specific verb and resource ("Set the episode's Longest automatic join fade in ms") with default value (40) and valid range (0-200), plus the null semantics. It also distinguishes itself from adjacent tools by naming fade_joins_tool and the manual-fade setters, so an agent can tell it apart from siblings without opening a schema.

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?

Explicitly frames when to use this versus alternatives: it is a ceiling, not an applied length, and "To give joins an exact length use ``fade_joins_tool`` with ``fade_ms``" — including the prerequisite of raising the limit first. It also tells the agent what this tool does NOT constrain (hand-set fades via set_clip_fade_tool/set_clips_fade_tool/set_clip_join_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