Skip to main content
Glama

clip_speed

Change a clip's playback speed by percentage, with optional timeline ripple and pitch correction, or set 0 for a freeze frame.

Instructions

Constant speed change (100 = normal, 50 = half speed slow-mo, 200 = 2x, 0 = freeze frame). ripple=true lets the timeline ripple to the new duration. Use clip_properties retime=optical_flow for smooth slow-mo.

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": {
      "clips": "<clips>",
      "percent": "<percent>"
    },
    "name": "clip_speed"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipsYes
rippleNo
percentYes
pitch_correctionNo
stretch_keyframesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose two important behaviors: percent=0 produces a freeze frame, and ripple=true extends the change to the timeline duration. However, it says nothing about whether the operation is reversible/undoable, what happens to existing keyframes when stretch_keyframes is false, or what pitch_correction does to audio.

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 with zero filler: the core semantics and scale come first, then behavioral modifiers and the sibling alternative. Every clause carries information an agent needs.

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

Completeness3/5

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

For a 5-parameter mutation tool with no annotations, no output schema, and no schema descriptions, the definition is only partially sufficient. It covers the primary parameter and one modifier well but leaves two parameters unexplained and says nothing about the response or the effect on neighboring clips beyond the ripple note.

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 all 5 parameters rely on the description. It explains percent thoroughly and clarifies ripple's effect, but pitch_correction and stretch_keyframes are never mentioned, leaving two ambiguous boolean parameters with null/default values undocumented anywhere.

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+resource (constant speed change on a clip) and immediately grounds it with a numeric scale (100 = normal, 50 = half speed, 200 = 2x, 0 = freeze frame). It also distinguishes itself from clip_properties, which is reserved for optical-flow retiming, so an agent can pick between them without opening either schema.

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?

It gives an explicit routing rule: use clip_properties with retime=optical_flow for smooth slow-mo, implying this tool is for constant speed changes. It also states the consequence of ripple=true, which is a usage decision. What's missing is a clear 'when not to use' for other cases, such as speed ramps or keyframed speed.

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