Skip to main content
Glama

clip_trim

Trim or extend a timeline clip by setting new start/end edges or head/tail offsets, with options to apply edits to linked audio/video and ripple-close gaps.

Instructions

Trim/extend a clip. Either give new timeline edges start/end (seconds/'120f'/TC), or head/tail deltas in seconds (positive = shorten, negative = extend into available source media). linked=true applies the same trim to linked audio/video. ripple=true closes the resulting gap after the clip.

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

Input Schema

NameRequiredDescriptionDefault
endNo
clipYes
headNo
tailNo
startNo
linkedNo
rippleNo

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 burden. It usefully discloses that negative deltas are limited by 'available source media', that `linked` propagates to linked audio/video, and that `ripple` closes the resulting gap — real behavioral context. It omits what happens if both edge and delta params are supplied, failure behavior when extending past available media, and 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?

Two dense sentences, front-loaded with the action, using backticked parameter names to keep each clause scannable. Every sentence conveys distinct, non-redundant information.

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 7-parameter mutation tool with no annotations and no output schema, the description covers most of what an agent needs: modes, units, sign conventions, and the side effects of `linked`/`ripple`. Still missing return-value expectations and edge-case/error behavior that would make it fully self-sufficient.

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

Parameters4/5

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

Schema coverage is 0%, so the description must compensate, and it largely does: it explains `start`/`end` accept seconds/'120f'/TC, gives sign semantics for `head`/`tail`, and clarifies `linked` and `ripple`. The required `clip` parameter and its identifier format are left unstated, and partial-specification cases (e.g. only `start`) are not addressed.

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?

States a specific verb+resource combination ('Trim/extend a clip') that an agent can distinguish from nearby siblings like clip_move or clip_speed based on the edge-vs-position semantics implied. It does not explicitly name or contrast with any sibling, so it stops short of a 5.

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?

Gives clear mode-selection guidance: use `start`/`end` for new timeline edges, or `head`/`tail` deltas with positive meaning shorten and negative meaning extend into source media. It also states the effects of `linked` and `ripple`. It offers no explicit when-not guidance or notes on conflicting modes beyond the 'Either ... or' framing.

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