Premiere Pro MCP Server

Navigate Playhead

navigate_playhead

Move the active-sequence playhead to start, end, in/out point, work-area bound, next/previous edit or marker, or step frames, then read the resulting position.

Instructions

Move the active-sequence playhead to the start, end, in/out point, work-area bound, next/previous edit or marker, or step a number of frames, then read back the resulting position. Navigation only; it never changes clips.

Input Schema

Name	Required	Description
`action`	Yes	Where to move the playhead.
`frames`	No	Frames to step for step_forward/step_backward (default 1).
`track_type`	No	Tracks whose clip edges count as edit points for next_edit/previous_edit (default both).
`track_index`	No	Restrict edit points to one track index.
`idempotency_key`	No	Optional client-chosen key (1-128 chars of A-Z a-z 0-9 . _ : -) for this intended edit. Pass a fresh key per edit and reuse it only when retrying that same edit, for example after a client-side timeout. A repeat with the same tool, key and arguments is not run again: while the first call is running it fails with IDEMPOTENCY_IN_PROGRESS (poll get_last_operations); after it finished it returns the original outcome marked replayed. A definite failure with nothing applied (receipt outcome not_applied) may be retried with the same key. Reusing a key with different arguments fails with IDEMPOTENCY_KEY_REUSED. Scoped to this MCP session (the stdio server process or one HTTP session) and held in memory only (200 keys, 1 hour); it does not survive a restart or reconnect. Read-only invocations are never deduplicated.
`expected_cep_target`	No	Optional reviewed CEP sequence/clip identity and exact tick ranges. Checked before every generated command; UXP refuses this CEP-only guard.
`expected_project_path`	No	Optional absolute saved-project path. Every generated CEP command refuses before its body when the active project differs or is unsaved. UXP commands refuse this CEP-only guard; local-only tools do not inspect Premiere. Omit to keep existing behavior.

Output 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.
`receipt`	No	Versioned common mutation receipt; success never implies rendered verification.
`idempotency`	No	Present when idempotency_key deduplicated this call: replayed is true when the original outcome was returned instead of running again.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.25.0Oct 24, 2026

addedInput schema / properties / idempotency_key

Added value: +{
+  "description": "Optional client-chosen key (1-128 chars of A-Z a-z 0-9 . _ : -) for this intended edit. Pass a fresh key per edit and reuse it only when retrying that same edit, for example after a client-side timeout. A repeat with the same tool, key and arguments is not run again: while the first call is running it fails with IDEMPOTENCY_IN_PROGRESS (poll get_last_operations); after it finished it returns the original outcome marked replayed. A definite failure with nothing applied (receipt outcome not_applied) may be retried with the same key. Reusing a key with different arguments fails with IDEMPOTENCY_KEY_REUSED. Scoped to this MCP session (the stdio server process or one HTTP session) and held in memory only (200 keys, 1 hour); it does not survive a restart or reconnect. Read-only invocations are never deduplicated.",
+  "maxLength": 128,
+  "minLength": 1,
+  "pattern": "^[A-Za-z0-9._:-]+$",
+  "type": "string"
+}

addedOutput schema / properties / idempotency

Added value: +{
+  "additionalProperties": true,
+  "description": "Present when idempotency_key deduplicated this call: replayed is true when the original outcome was returned instead of running again.",
+  "type": "object"
+}

Changed3 schema fields changedv1.24.0Oct 12, 2026

addedInput schema / properties / expected_cep_target

Added value: +{
+  "additionalProperties": false,
+  "anyOf": [
+    {
+      "required": [
+        "sequence_id"
+      ]
+    },
+    {
+      "required": [
+        "source_item"
+      ]
+    }
+  ],
+  "description": "Optional reviewed CEP sequence/clip identity and exact tick ranges. Checked before every generated command; UXP refuses this CEP-only guard.",
+  "properties": {
+    "backend": {
+      "const": "cep",
+      "description": "Backend namespace for these IDs.",
+      "type": "string"
+    },
+    "clip": {
+      "additionalProperties": false,
+      "description": "Optional exact reviewed timeline clip.",
+      "properties": {
+        "effect": {
+          "additionalProperties": false,
+          "description": "Reviewed effect and parameter identity checked before mutation.",
+          "properties": {
+            "display_name": {
+              "description": "Optional exact host display name.",
+              "maxLength": 512,
+              "minLength": 1,
+              "type": "string"
+            },
+            "match_name": {
+              "description": "Effect match name from host inspection.",
+              "maxLength": 512,
+              "minLength": 1,
+              "type": "string"
+            },
+            "parameter_index": {
+              "description": "Inspected zero-based parameter index.",
+              "maximum": 255,
+              "minimum": 0,
+              "type": "integer"
+            },
+            "parameter_name": {
+              "description": "Exact inspected parameter name.",
+              "maxLength": 512,
+              "minLength": 1,
+              "type": "string"
+            }
+          },
+          "required": [
+            "match_name",
+            "parameter_index",
+            "parameter_name"
+          ],
+          "type": "object"
+        },
+        "end_ticks": {
+          "description": "Exact expected exclusive timeline end ticks.",
+          "pattern": "^-?\\d{1,30}$",
+          "type": "string"
+        },
+        "in_ticks": {
+          "description": "Exact expected source In ticks.",
+          "pattern": "^-?\\d{1,30}$",
+          "type": "string"
+        },
+        "node_id": {
+          "description": "Stable CEP node ID.",
+          "maxLength": 512,
+          "minLength": 1,
+          "type": "string"
+        },
+        "out_ticks": {
+          "description": "Exact expected exclusive source Out ticks.",
+          "pattern": "^-?\\d{1,30}$",
+          "type": "string"
+        },
+        "project_item_id": {
+          "description": "Expected source project-item node ID.",
+          "maxLength": 512,
+          "minLength": 1,
+          "type": "string"
+        },
+        "start_ticks": {
+          "description": "Exact expected timeline start ticks.",
+          "pattern": "^-?\\d{1,30}$",
+          "type": "string"
+        },
+        "track_index": {
+          "description": "Expected zero-based track index; identity still checked.",
+          "maximum": 255,
+          "minimum": 0,
+          "type": "integer"
+        },
+        "track_type": {
+          "description": "Expected media track group.",
+          "enum": [
+            "video",
+            "audio"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "node_id",
+        "track_type",
+        "track_index"
+      ],
+      "type": "object"
+    },
+    "project_document_id": {
+      "description": "Exact Premiere project document ID observed during review.",
+      "maxLength": 512,
+      "minLength": 1,
+      "type": "string"
+    },
+    "sequence_id": {
+      "description": "Stable expected active sequence ID.",
+      "maxLength": 512,
+      "minLength": 1,
+      "type": "string"
+    },
+    "source_item": {
+      "additionalProperties": false,
+      "description": "Reviewed source identity for a source-only operation.",
+      "properties": {
+        "media_path": {
+          "description": "Optional exact source-media path.",
+          "maxLength": 4096,
+          "minLength": 1,
+          "type": "string"
+        },
+        "node_id": {
+          "description": "Exact project-item node ID.",
+          "maxLength": 512,
+          "minLength": 1,
+          "type": "string"
+        }
+      },
+      "required": [
+        "node_id"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "backend"
+  ],
+  "type": "object"
+}

addedInput schema / properties / expected_project_path

Added value: +{
+  "description": "Optional absolute saved-project path. Every generated CEP command refuses before its body when the active project differs or is unsaved. UXP commands refuse this CEP-only guard; local-only tools do not inspect Premiere. Omit to keep existing behavior.",
+  "maxLength": 4096,
+  "minLength": 1,
+  "type": "string"
+}

addedOutput schema / properties / receipt

Added value: +{
+  "additionalProperties": true,
+  "description": "Versioned common mutation receipt; success never implies rendered verification.",
+  "type": "object"
+}

Changed1 schema field changedv1.18.6Sep 30, 2026

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.16.1Sep 18, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish that this is not read-only, not destructive, and not idempotent. The description adds meaningful context by saying it reads back the resulting position and never changes clips, which clarifies the mutation is limited to playhead/navigation state. It does not restate contradiction against annotations.

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 tight sentences, front-loads the primary behavior, and ends with an important scope constraint. Every clause contributes to understanding what the tool does and what it does not do.

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 an output schema and fully described parameters, the description gives enough context for an agent to understand the tool's core navigation behavior and its non-destructive-to-clips scope. It omits details about idempotency and CEP guard parameters, but those are covered in the schema, so the description is largely complete for selection and basic 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 description coverage is 100%, so the detailed parameter semantics are already carried by the schema. The description summarizes the available actions but adds little beyond the action enum and does not explain frames, track_type, track_index, idempotency_key, or the expected_* guard parameters. A baseline 3 is appropriate.

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 states a specific verb and resource: moving the active-sequence playhead, with an explicit list of destinations and frame stepping. It also distinguishes the tool from clip-editing operations by saying it is 'Navigation only; it never changes clips.' It does not explicitly differentiate from close siblings such as set_playhead_position, move_playhead_to_edit, or get_next_edit_point, so it falls short of full sibling clarity.

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 enumeration of actions implies when the tool is useful: moving to sequence boundaries, in/out points, work-area bounds, edits, markers, or stepping frames. However, it does not state when to prefer this over related tools like set_playhead_position or move_playhead_to_edit, nor does it provide exclusions or alternatives.

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

Deploy Server