Premiere Pro MCP Server

Get Workspaces

get_workspaces

Read-onlyIdempotent

Lists all available workspace layouts in Premiere Pro, helping you identify the panel arrangement to use for a specific editing task.

Instructions

List all available workspace layouts in Premiere Pro

Input Schema

Name	Required	Description	Default
`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.

Changed1 schema field changedv1.25.0Oct 24, 2026

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 / additionalProperties
```
Added value: +false
```

addedInput schema / properties

Added value: +{
+  "expected_cep_target": {
+    "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"
+  },
+  "expected_project_path": {
+    "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."

Changed1 schema field changedv1.14.9Sep 8, 2026
- removedInput schema / properties
```
Removed value: -{}
```

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

First observedv1.1.1May 28, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds no further behavioral context, such as whether a live Premiere connection is required or how the two guard parameters affect execution.

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?

A single front-loaded sentence with zero filler. It is appropriately sized for a simple read tool, though it is so brief that it leaves no room for the routing context a multi-hundred-sibling toolset would benefit from.

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?

An output schema exists, so return values need not be described, and annotations carry the safety semantics. Combined with 100% schema coverage on the optional guard parameters, the definition is complete enough for an agent to call it correctly.

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% and both parameters are optional guards fully documented in the schema, so the description need not compensate. It mentions neither expected_cep_target nor expected_project_path, so it adds nothing beyond the schema, but that is acceptable at this coverage level.

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?

States a specific verb and resource ('List all available workspace layouts in Premiere Pro'), which an agent can cleanly separate from the sibling mutation tool set_workspace. It stops short of explicitly naming that sibling pair, but the read-vs-set distinction is unambiguous from the wording.

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: an agent infers this is the discovery step to run before set_workspace. There is no explicit when-to-use, when-not-to-use, or named alternative.

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

Deploy Server