Premiere Pro MCP Server

Set Clip Duration

set_clip_duration

Change a timeline clip's visible duration by moving only its end while keeping its start fixed. Extend still images beyond import length and apply the edit to linked audio/video partners.

Instructions

Set one timeline clip's visible duration by moving only its timeline end (TrackItem.end) while keeping its start fixed. Pass exactly one of duration_seconds or end_seconds. Works for extending still images past their import length. Refuses to overlap the next clip on the same track, rejects shortening that would strand effect keyframes unless keyframe_policy is preserve, reads start/end back, and restores the original end if Premiere clamps or ignores the write (for example when video media has no handle left). Linked audio/video partners get the same change by default (include_linked), applied as the same end offset so partners with a J/L cut keep their offset; every clip is checked before any is changed. Use this instead of speed changes, which Premiere does not expose to scripting.

Input Schema

TableJSON Schema

Name	Required	Description
`node_id`	Yes	Node ID of the timeline clip (track item) to resize
`end_seconds`	No	Target absolute timeline end (out-point) in seconds. Must be at least one frame after the clip's start. Specify exactly one of duration_seconds or end_seconds.
`include_linked`	No	Also apply the edit to the clip's linked audio/video partners, as Premiere does with linked selection (default: true).
`keyframe_policy`	No	When shortening, how to handle effect keyframes beyond the new visible length: reject (default) leaves the timeline unchanged; preserve keeps them and reports their count.
`duration_seconds`	No	Target visible duration in seconds, measured from the clip's current timeline start. Specify exactly one of duration_seconds or end_seconds.

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

Addedv1.18.0Sep 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Adds substantial behavior beyond the annotations: atomic pre-checking across all clips, refusal to overlap the next clip, keyframe-stranding rejection unless keyframe_policy=preserve, read-back verification, and restoration of the original end if Premiere clamps or ignores the write. It also discloses the linked-partner default and the same-end-offset rule that preserves J/L cuts. This is far richer than the readOnly/destructive/idempotent hints.

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?

One dense paragraph, but front-loaded with the core action before the constraints and edge cases. Each clause carries real information (atomicity, clamp fallback, keyframe policy, linked offset). It is slightly overloaded and would read better split into behavior vs. constraints, but nothing is wasted.

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?

A mutation tool with five parameters and an output schema; the description covers the failure modes, safety guarantees, and default behaviors an agent needs before invoking. Return values need not be explained since an output schema exists. Nothing material 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 description coverage is 100%, so the baseline is 3. The description nonetheless reinforces the mutual-exclusivity of duration_seconds/end_seconds and, more importantly, adds cross-parameter semantics absent from the schema: include_linked partners receive the change applied as the same end offset, preserving J/L cuts. That interaction knowledge justifies a step above baseline.

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?

Names a specific verb (set), resource (one timeline clip's visible duration), and implementation detail (moves only TrackItem.end while keeping start fixed). This immediately distinguishes it from siblings like set_clip_start_time, trim_clip, and move_clip. It also closes with a redirect for the adjacent use case (speed changes).

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?

Explicitly routes the agent to alternatives: 'Use this instead of speed changes, which Premiere does not expose to scripting.' It also states the exclusivity rule for duration_seconds vs end_seconds and the still-image extension use case. It does not, however, contrast with the other trimming siblings (trim_clip, set_clip_start_time), so routing is partially covered.

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

Deploy Server