Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Trim Clip

trim_clip

Trim a clip's source in or out point and verify the matching visible timeline edge. Refuse retimed clips and, by default, reject trims that would leave effect keyframes outside the visible clip.

Instructions

Trim exactly one source in/out point and verify the corresponding visible timeline edge. Refuses retimed clips and, by default, trims that would leave effect keyframes outside the visible clip.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
node_idYesNode ID of the clip to trim
new_in_secondsNoNew source in-point in seconds (relative to the clip's source media). Specify exactly one edit point.
keyframe_policyNoHow to handle effect keyframes beyond the trimmed visible range: reject (default) leaves the timeline unchanged; preserve explicitly keeps them and reports their count.
new_out_secondsNoNew source out-point in seconds (relative to the clip's source media). Specify exactly one edit point.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the tool completed successfully.
dataNoTool-specific result data when ok is true.
toolYesThe registered MCP tool name.
errorNoFailure detail when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.14.9
    • addedInput schema / properties / new_in_seconds / minimum
      Added value: +0
    • addedInput schema / properties / new_out_seconds / minimum
      Added value: +0
  2. Changed2 schema fields changedv1.14.4
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "description": "Tool-specific result data when ok is true."
+    },
+    "error": {
+      "description": "Failure detail when ok is false.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "Whether the tool completed successfully.",
+      "type": "boolean"
+    },
+    "tool": {
+      "description": "The registered MCP tool name.",
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok",
+    "tool"
+  ],
+  "type": "object"
+}
  3. Changed3 schema fields changedv1.11.3
    • addedInput schema / properties / keyframe_policy
      Added value: +{
+  "description": "How to handle effect keyframes beyond the trimmed visible range: reject (default) leaves the timeline unchanged; preserve explicitly keeps them and reports their count.",
+  "enum": [
+    "reject",
+    "preserve"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / new_in_seconds / description
      Previous value: -"New in-point in seconds (relative to clip's source media)"New value: +"New source in-point in seconds (relative to the clip's source media). Specify exactly one edit point."
    • changedInput schema / properties / new_out_seconds / description
      Previous value: -"New out-point in seconds (relative to clip's source media)"New value: +"New source out-point in seconds (relative to the clip's source media). Specify exactly one edit point."
  4. Changed1 schema field changedv1.4.0
    • removedInput schema / additionalProperties
      Removed value: -false
  5. First observedv1.1.1

TDQS

A4/5.0
Behavior4/5

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

The annotations provide only basic safety hints, so the description carries the behavioral burden. It discloses two meaningful refusal conditions: retimed clips are rejected, and trims that would push effect keyframes outside the visible clip are rejected by default. It also claims the tool verifies the visible timeline edge, adding transparency beyond the structured fields.

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?

The description is two focused sentences with no filler. The core action is stated first, followed by the most important edge-case constraints, making it easy for an agent to parse quickly.

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?

Given the output schema exists and the input schema is fully documented, the description covers the main behavioral context: single-point trimming, retimed clip refusal, and default keyframe handling. It could go slightly further by explaining what 'verify the corresponding visible timeline edge' means in terms of return or side effects, but overall it is sufficiently complete for correct invocation.

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 coverage is 100%, and the parameter descriptions already explain node_id, new_in_seconds, new_out_seconds, and keyframe_policy in detail. The description reinforces the 'exactly one edit point' rule and the default keyframe rejection behavior, but does not add significant new parameter meaning beyond what the schema already provides.

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: 'Trim exactly one source in/out point' on a clip, and it explicitly narrows the operation to exactly one edit point. It also distinguishes the behavior from sibling tools like slip_edit or move_clip by emphasizing the verification of the visible timeline edge.

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 intended use is implied clearly: trim a single clip in or out point in the timeline. However, the description does not name alternative tools or state when to prefer another operation, such as slip_edit or roll_edit. It only gives refusal conditions for retimed clips and keyframe behavior, which is context but not explicit selection guidance.

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

Deploy Server

Other Tools