Premiere Pro MCP Server

Trim Clip

trim_clip

Trim a clip's source in/out point while keeping linked audio/video in sync and preventing overlaps or keyframe loss. Specify one edit point; refuses unknown durations or retimed clips.

Instructions

Trim exactly one source in/out point and verify the corresponding visible timeline edge. Requires accessible physical media duration from ffprobe; unknown duration or linked partners using different source files refuse before mutation. Refuses retimed clips, extensions that would overlap the neighbouring clip on the same track, and, by default, trims that would leave effect keyframes outside the visible clip. Linked audio/video partners get the same trim by default (include_linked), applied as the same offset from each partner's own source point so a J/L cut or slipped audio stays in sync; every clip is checked before any is changed. To set a clip's timeline length or extend a still image, use set_clip_duration.

Input Schema

TableJSON Schema

Name	Required	Description
`node_id`	Yes	Node ID of the clip to trim
`include_linked`	No	Also apply the edit to the clip's linked audio/video partners, as Premiere does with linked selection (default: true).
`new_in_seconds`	No	New source in-point in seconds (relative to the clip's source media). Specify exactly one edit point.
`keyframe_policy`	No	How 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_seconds`	No	New source out-point in seconds (relative to the clip's source media). Specify exactly one edit point.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	Whether the tool completed successfully.
`data`	No	Tool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it.
`tool`	Yes	The registered MCP tool name.
`error`	No	Failure detail when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.18.6Sep 30, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / include_linked

Added value: +{
+  "description": "Also apply the edit to the clip's linked audio/video partners, as Premiere does with linked selection (default: true).",
+  "type": "boolean"
+}

changedOutput schema / properties / data / description

Previous value: -"Tool-specific result data when ok is true."New value: +"Tool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it."

Changed2 schema fields changedv1.14.9Sep 8, 2026
- addedInput schema / properties / new_in_seconds / minimum
```
Added value: +0
```
- addedInput schema / properties / new_out_seconds / minimum
```
Added value: +0
```

Changed2 schema fields changedv1.14.4Aug 29, 2026

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"
+}

Changed3 schema fields changedv1.11.3Aug 19, 2026

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."

Changed1 schema field changedv1.4.0Jul 27, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedv1.1.1May 28, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations declare it is not read-only and not destructive, but the description adds substantial behavioral detail: it requires ffprobe duration, refuses before mutation on specific conditions, applies the same trim to linked partners with offset preservation, checks every clip before any change, and explains keyframe handling. This is well beyond what annotations provide.

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?

Front-loaded with the core action and then requirements, refusals, linked behavior, and an alternative. Dense but every sentence carries specific, non-redundant information. Slightly long but justified by the tool's complexity.

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

Completeness5/5

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

Given the tool's complexity, the description covers prerequisites, refusal conditions, linked-partner semantics, keyframe policy, and an alternative tool. Output schema exists, so return values need not be explained. Nothing critical for correct invocation is missing.

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 100% so all parameters are already documented in the schema. The description adds meaning by explaining the linked-partner offset behavior ('same offset from each partner's own source point so a J/L cut or slipped audio stays in sync') and clarifying keyframe_policy default behavior, which enriches understanding beyond the schema text.

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?

Starts with a specific verb and resource: 'Trim exactly one source in/out point and verify the corresponding visible timeline edge.' Clearly distinguishes itself from the named alternative set_clip_duration by scope, and the agent can immediately tell what operation is performed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly names set_clip_duration as the correct tool for setting timeline length or extending stills, and lists clear preconditions and refusal conditions (unknown duration, linked partners with different source files, retimed clips, overlapping extensions, keyframe policy). No inference needed for when to use or avoid this tool.

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

Deploy Server