Skip to main content
Glama

apply_cuts

Applies a cut plan in Premiere Pro or DaVinci Resolve to create a new sequence with only kept ranges, leaving the original unchanged; standalone mode sets the timeline for render export.

Instructions

Apply a cut plan in the active editor. Premiere/Resolve: creates a NEW sequence with only the kept ranges (original untouched). Standalone: sets the timeline that render will export.

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": {
      "planId": "<planId>"
    },
    "name": "apply_cuts"
  }
}

Input Schema

NameRequiredDescriptionDefault
planIdYes
sequenceNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses that the operation is non-destructive ("original untouched"), creates a new sequence, and behaves differently depending on host. It omits failure behavior for an invalid planId and does not describe return values, which matters since no output schema exists.

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?

Three short sentences, front-loaded with the action, then the host-specific consequences. No filler and no redundancy.

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?

Behavioral impact is explained well for a mutation tool with no annotations, but the definition leaves the parameters undocumented and says nothing about outcome or failure modes, which is a real gap for a 2-param tool with no output schema.

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 coverage is 0%, so the description must explain both parameters and it does not. "planId" is only loosely inferable from "apply a cut plan," and "sequenceName" is never mentioned at all, even though the description references creating a new sequence that this parameter presumably names.

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 gives a specific verb+resource ("Apply a cut plan in the active editor") and explains the concrete outcome in each host context: a NEW sequence in Premiere/Resolve versus setting the export timeline in standalone mode. That distinguishes it from plan_cuts and render implicitly, but it never names those siblings or states the relationship outright.

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 only implied: you apply a plan that presumably came from plan_cuts, and the standalone branch feeds render. There is no explicit when-to-use/when-not statement, no precondition such as the plan needing to exist, and no guidance on choosing between this and show_plan or render.

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