Skip to main content
Glama

razor

Cut clips at one or more timeline times on selected or all unlocked video/audio tracks while preserving linked clip cuts, grades, properties, fades, and comps.

Instructions

Cut (blade) clips at one or more timeline times. tracks: limit to e.g. ["V1","A1"] (default: all unlocked video+audio tracks; linked clips are always cut together). Grades/properties/fades/comps are preserved.

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": {
      "times": "<times>"
    },
    "name": "razor"
  }
}

Input Schema

NameRequiredDescriptionDefault
timesYes
tracksNo
keep_gradesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/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, and it does disclose meaningful behavior: defaults to all unlocked video+audio tracks, linked clips are cut together, and grades/properties/fades/comps survive the cut. It omits whether the operation is undoable or what happens to locked tracks, which matters for a timeline-mutating tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact sentences with the core action front-loaded, followed by scoping and preservation guarantees. The parenthetical is dense but every clause carries operational information; no filler.

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 3-parameter mutation tool with no annotations, no output schema, and zero schema description coverage, the definition covers the critical semantics but leaves gaps: the `times` format, explicit treatment of `keep_grades`, and the return/confirmation behavior are unstated.

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 does well for `tracks` (example values, default scope) and implicitly for `times` ('one or more timeline times'). `keep_grades` is never named — only hinted at by 'Grades/properties... are preserved' — and no time format (frames vs timecode) is given.

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 and resource: 'Cut (blade) clips at one or more timeline times', which is concretely distinct from trimming or deleting. It does not explicitly contrast with siblings like clip_trim or clips_delete, so it stops just 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 Guidelines3/5

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

The description implies when the tool applies (splitting clips at given timeline positions) and clarifies the default track scope, but it never states when to prefer it over clip_trim or clips_delete, nor any prerequisites. Usage is inferable rather than guided.

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