Premiere Pro MCP Server

Set Scale Width Height

set_scale_width_height

Set independent width and height scale on a clip: disables Uniform Scale, writes both values, and verifies they read back to confirm the resize.

Instructions

Set independent width and height scale on a clip. Turns Uniform Scale off, writes Motion > Scale Width (width) and Motion > Scale (which Premiere uses as the height once Uniform Scale is off), then reads all three back. Fails when a value does not read back.

Input Schema

TableJSON Schema

Name	Required	Description
`node_id`	Yes	Node ID of the clip
`scale_width`	Yes	Scale width percentage (0-10000)
`scale_height`	Yes	Scale height percentage (0-10000). Written to Motion > Scale, which is the height when Uniform Scale is off.

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.

Changed4 schema fields changedv1.18.6Sep 30, 2026

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

changedInput schema / properties / scale_height / description

Previous value: -"Scale height percentage"New value: +"Scale height percentage (0-10000). Written to Motion > Scale, which is the height when Uniform Scale is off."

changedInput schema / properties / scale_width / description

Previous value: -"Scale width percentage"New value: +"Scale width percentage (0-10000)"

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.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.4.0Jul 27, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedv1.1.1May 28, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations, the description discloses key behavioral traits: it turns Uniform Scale off, writes to specific Motion properties, reads all three values back, and fails when a value does not read back. This gives the agent important side-effect, verification, and failure-condition context that the annotations do not provide.

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 three tightly written sentences, front-loaded with the primary action and followed by the exact write sequence and failure condition. Every sentence contributes necessary operational detail with no redundancy.

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 mutation nature of the tool, the annotations, the fully described input schema, and the presence of an output schema, the description is complete. It covers the key side effect, the exact property writes, the read-back verification, and the failure mode, leaving nothing critical for the agent to guess.

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 the schema already documents all three parameters. The description adds meaningful mapping detail beyond the schema by clarifying that width is written to Motion > Scale Width and height is written to Motion > Scale when Uniform Scale is off, which helps the agent understand the underlying Premiere behavior.

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?

The description states a specific verb and resource: set independent width and height scale on a clip. It also distinguishes this operation from uniform scaling by explicitly noting that it turns Uniform Scale off, which separates it from siblings like set_uniform_scale and set_clip_scale.

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 description implies the use case through its mechanism (independent width and height scaling, Uniform Scale off), but it does not explicitly state when to choose this tool over alternatives like set_clip_scale or set_uniform_scale. No exclusions or prerequisites are given, so the agent must infer the appropriate context.

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

Deploy Server