Premiere Pro MCP Server

Set Clip Properties

set_clip_properties

Modify clip opacity, scale, position, and rotation. Supplying unsupported speed returns an actionable error before any change.

Instructions

Set supported clip properties (opacity, scale, position, rotation). Clip speed is unsupported and fails before mutation.

Input Schema

TableJSON Schema

Name	Required	Description
`scale`	No	Scale percentage (100 = original size)
`speed`	No	Unsupported by Premiere's public scripting APIs. Supplying this returns an actionable error without mutating the clip.
`node_id`	Yes	Node ID of the clip
`opacity`	No	Opacity value (0-100)
`rotation`	No	Rotation in degrees
`position_x`	No	Horizontal position
`position_y`	No	Vertical position

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

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

Changed1 schema field changedv1.11.5Aug 22, 2026

changedInput schema / properties / speed / description

Previous value: -"Playback speed multiplier (1.0 = normal, 2.0 = double speed)"New value: +"Unsupported by Premiere's public scripting APIs. Supplying this returns an actionable error without mutating the clip."

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

TDQS

B3.3/5.0

Behavior3/5

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

The description adds useful behavioral context beyond the annotations by stating that clip speed is unsupported and fails before mutation, implying the operation is safe when an unsupported parameter is supplied. However, it does not clarify whether omitted properties are preserved or reset, nor does it describe partial-update behavior or other failure modes.

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 a single, front-loaded sentence with no wasted words. It immediately states the action and resource, enumerates the supported properties, and adds the key unsupported-speed caveat in a compact second clause.

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

Completeness3/5

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

The description gives enough to identify the tool and the main unsupported property, but it does not fully cover important invocation semantics for a mutation tool: whether unspecified properties remain unchanged, whether all supported properties can be set together atomically, or how this setter relates to the dedicated single-property setters. The output schema exists, but behavioral completeness is still limited.

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?

Since the input schema already documents all seven parameters with 100% coverage, the description need not repeat definitions. The description does group parameters conceptually (opacity, scale, position, rotation) and highlights the speed caveat, but it does not add meaning beyond the schema descriptions.

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 ('Set supported clip properties') and enumerates the affected properties: opacity, scale, position, rotation. It does not explicitly distinguish itself from sibling tools like set_clip_properties_batch or individual setters such as set_clip_opacity, so it falls short of full sibling differentiation.

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

Usage Guidelines2/5

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

The description gives no guidance on when to prefer this tool over the many related siblings, such as set_clip_opacity, set_clip_scale, or set_clip_properties_batch. It does note that speed is unsupported, but it does not direct the agent to an alternative or explain when this multi-property setter is the right choice.

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

Deploy Server