Skip to main content
Glama
Podcast MCP
by calebn

set_clips_fade_tool

Adjust fade-in and fade-out durations across multiple audio clips in one operation, with optional curve types and a single undo step.

Instructions

Add a delta (ms, negative shortens) to the fade-in and fade-out of several clips at once.

One undo step covers every clip. Each clip is bounded by its own length like set_clip_fade_tool, not by the Longest automatic join fade. A curve (linear, equal_power or s) is set on every named clip; left out, each clip keeps its own. A clip changed since it was read returns clip_fade_changed and no clip changes.

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_ids": "<clip_ids>"
    },
    "name": "set_clips_fade_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
clip_idsYes
project_pathNo
fade_in_curveNo
fade_out_curveNo
fade_in_delta_msNo
fade_out_delta_msNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.4

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral burden well: it discloses one undo step for all clips, per-clip length bounding, curve inheritance, and atomic failure when a clip changed since read. It stops short of covering all edge cases, such as what happens when a negative delta would reduce a fade below zero.

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 action and then layers on the important scoping, undo, bounding, curve, and atomicity details. Every sentence contributes distinct operational meaning with no filler.

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?

For a batch mutation tool with no annotations but a rich output schema, the description provides enough behavioral context to call it correctly: batch scope, delta semantics, undo behavior, per-clip bounds, curve handling, and stale-read atomicity. The remaining schema-level details are appropriately left to the schema.

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?

The description adds meaningful semantics beyond the schema: deltas are milliseconds where negative shortens, curves accept linear/equal_power/s, and omitted curves preserve each clip's current curve. It does not explain the optional project_path parameter, so one of the six parameters remains only schema-documented.

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?

The description states a specific batch mutation: adding a millisecond delta to fade-in and fade-out across several clips. It explicitly contrasts this with the single-clip behavior of ``set_clip_fade_tool`` and with the Longest automatic join fade, so the agent can distinguish it from siblings.

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

Usage Guidelines4/5

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

The description makes clear when to use this tool: when applying a fade delta to several clips at once, with a separate single-clip alternative referenced. It does not spell out every when-not condition, but the batch scope and single-clip contrast provide strong routing 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