Skip to main content
Glama
Sign In

CutClip.one

by one.cutclip
OverviewDiscussionsAdmin

timeline.remove_transition

Remove a transition. For a crossfade or smooth_blend this also shifts the incoming clip back to its pre-transition position.

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": {
      "projectId": "<projectId>",
      "expectedVersion": "<expectedVersion>",
      "transitionItemId": "<transitionItemId>"
    },
    "name": "timeline.remove_transition"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYes
expectedVersionYes
transitionItemIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose one genuinely useful side effect: crossfade and smooth_blend removals shift the incoming clip back to its pre-transition position. It says nothing about whether the removal is undoable, what happens to the outgoing clip, or how expectedVersion conflicts are handled.

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 short sentences, front-loaded with the core action and followed immediately by the non-obvious side effect. No filler or redundant restatement of the name.

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?

This is a destructive mutation with no annotations, no output schema, and zero parameter documentation, so the description should do more. It covers the side effect but leaves the concurrency contract, undo behavior, and sibling disambiguation unaddressed.

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% across three required parameters, and the description adds no meaning for any of them. Most notably, expectedVersion is a concurrency token whose semantics (optimistic locking, failure on mismatch) are entirely undocumented, and transitionItemId is never tied to how an agent would obtain it.

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 description states a specific verb and resource ('Remove a transition'), which is unambiguous on its own. It does not, however, distinguish itself from the sibling timeline.remove_transitions (plural) or explain the relationship to timeline.add_transition, so an agent must infer the singular-vs-batch split.

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?

There is no guidance on when to use this versus timeline.remove_transitions, which is the obvious alternative for the same operation. No prerequisites, no mention of what state the timeline must be in, and no exclusions are given.

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

All CutClip.one toolsInspect
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.

Resources