cuttingfloor

Remove clip

clip.remove

Idempotent

Remove a clip and the clips linked to it; ripple closes the gap. Returns the edit result (see the server instructions).

Input Schema

Name	Required	Description	Default
`ripple`	No	Close the gap by pulling later clips left
`clip_id`	Yes
`preview`	No	inline: image in the result; link: URI that renders on read; none	link
`timeline_id`	Yes	Timeline handle; every edit returns a new one
`other_tracks`	No	What the other tracks do when this edit moves later clips on the clip's own tracks (linked clips always move with it). stay: they don't move, and the result warns which clips there now play early or late. sync: they get the same change, so titles, overlays and sound stay in step: time taken out here comes out of them too (like range.extract), time added here opens the same gap in them (clips crossing that point are split, as insert does). Locked tracks always stay	stay

Output Schema

Name	Required	Description
`parent`	Yes	Timeline handle; every edit returns a new one
`changed`	Yes
`clip_id`	No
`preview`	Yes
`clip_ids`	No
`track_id`	No
`warnings`	Yes
`timeline_id`	Yes	Timeline handle; every edit returns a new one

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 25, 2026

TDQS

B3/5.0

Behavior1/5

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

The description says 'Remove a clip', which is a destructive operation, while annotations declare destructiveHint: false. This direct contradiction misleads the agent about the tool's safety profile. Although annotations provide other hints (readOnlyHint: false, idempotentHint: true), the contradiction is severe.

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 sentences with zero waste: the first front-loads the action and scope, the second succinctly notes the return. No redundancy or fluff.

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

Completeness2/5

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

For a mutation tool with 5 parameters and an output schema, the description is minimal. The contradiction with destructiveHint undermines completeness, as an agent cannot reliably infer the tool's safety. The mention of 'Returns the edit result' is helpful but insufficient to compensate.

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 80%, so the schema already documents most parameters (ripple, preview, timeline_id, other_tracks). The description only hints at 'ripple' without adding syntax or format details. Baseline 3 is appropriate given the high coverage.

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 verb ('Remove') and resource ('clip'), and clarifies scope by including 'the clips linked to it'. It also mentions the ripple effect, making the action unambiguous and distinguishable from siblings like clip.unlink or clip.trim.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives (e.g., clip.unlink or range.extract). The description implies usage through behavior ('ripple closes the gap') but does not state conditions for selection or exclusion.

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

All cuttingfloor 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.