Cutible MCP Server

ripple_delete

Delete a video clip and automatically close the gap left in the timeline, keeping the sequence continuous.

Instructions

Delete a clip and close the gap.

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>"
    },
    "name": "ripple_delete"
  }
}

Input Schema

Name	Required	Description	Default
`clip_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 14, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It does disclose that the tool is destructive and that it closes the resulting gap, but it does not say whether media is removed from disk or only the timeline, or whether the operation is reversible.

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 a single seven-word sentence with no filler or redundant content. It states the action and the key side effect with maximum economy.

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?

Given that this is a one-parameter destructive tool with no output schema and no annotations, the description covers the core invocation details: what action is performed, what resource is affected, and what side effect results. It is sufficient for an agent to call the tool correctly, though it could add irreversibility context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description adds no detail about the required clip_id parameter beyond its name. The role of clip_id is inferable from the tool's purpose, but the description itself does not compensate for the missing schema documentation.

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 uses a specific verb-object pair, 'Delete a clip', and adds the unique ripple behavior, 'close the gap'. This is enough to distinguish it from all sibling tools, none of which perform a plain clip deletion.

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?

The description gives no when-to-use guidance, no exclusion criteria, and names no alternatives. An agent cannot tell from the description when to prefer this over trim, split, or remove_silences.

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