Skip to main content
Glama
Sign In

CutClip.one

by one.cutclip
OverviewDiscussionsAdmin

timeline.set_speed

Change a clip's playback speed (0.2 = 5x slower, 1 = normal, 1.8 = 1.8x faster). Recomputes the clip's timeline duration for the new speed and ripples everything later on the same track to stay contiguous — the source range consumed is unchanged, only how long it takes to play.

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>",
      "itemId": "<itemId>",
      "speed": "<speed>"
    },
    "name": "timeline.set_speed"
  }
}

Input Schema

NameRequiredDescriptionDefault
speedYes
itemIdYes
projectIdYes
expectedVersionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full load and does well: it discloses that timeline duration is recomputed, that later items on the same track ripple to stay contiguous, and that the consumed source range is unaffected. The main gap is that optimistic-concurrency behavior around expectedVersion (what happens on a version mismatch) is never mentioned.

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 tight sentences that front-load the action and the numeric scale, then explain the side effect. Every clause carries information; nothing is repeated from the schema except the min/max values, which are given concrete interpretation.

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?

For a four-parameter mutation with no annotations and no output schema, the description covers the operation's core semantics and consequences well. It falls short only on version-conflict/error behavior and on identifying a clip by itemId versus other timeline entities.

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 0%, so the description must compensate. It substantially clarifies the 'speed' parameter's scale and direction, which the schema only bounds at 0.2–1.8, but says nothing about itemId, projectId, or expectedVersion — notably the concurrency token, which a caller must understand to avoid failures.

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 names a specific verb and resource ('Change a clip's playback speed') and immediately disambiguates the meaning of the numeric scale (0.2 = 5x slower, 1 = normal, 1.8 = 1.8x faster). No sibling tool in the timeline.* family does this, so an agent can select it without opening other schemas.

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

Usage Guidelines3/5

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

Usage is implied through the described effect (durational change with ripple), but the description never states when to use this versus trim_item, move_item, or split_item, nor any preconditions such as the clip needing to exist or the timeline being unlocked. Helpful context exists, but explicit routing guidance does not.

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