Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Set Clip Properties

set_clip_properties

Set a clip's opacity, scale, position, and rotation in Premiere Pro. Speed changes are unsupported; use set_clip_duration to alter timeline length.

Instructions

Set supported clip properties (opacity, scale, position, rotation) and read each requested value back. Clip speed is unsupported and fails before mutation; use set_clip_duration to change a clip's timeline length.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scaleNoScale percentage (0-10000; 100 = original size)
speedNoUnsupported by Premiere's documented scripting APIs. Supplying this returns an actionable error without mutating the clip; use set_clip_duration to change timeline length.
node_idYesNode ID of the clip
opacityNoOpacity value (0-100)
rotationNoRotation in degrees
position_xNoHorizontal position in sequence pixels
position_yNoVertical position in sequence pixels

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the tool completed successfully.
dataNoTool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it.
toolYesThe registered MCP tool name.
errorNoFailure detail when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.19.0
    • addedInput schema / properties / opacity / maximum
      Added value: +100
    • addedInput schema / properties / opacity / minimum
      Added value: +0
    • changedInput schema / properties / scale / description
      Previous value: -"Scale percentage (100 = original size)"New value: +"Scale percentage (0-10000; 100 = original size)"
    • addedInput schema / properties / scale / maximum
      Added value: +10000
    • addedInput schema / properties / scale / minimum
      Added value: +0
  2. Changed4 schema fields changedv1.18.6
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / position_x / description
      Previous value: -"Horizontal position"New value: +"Horizontal position in sequence pixels"
    • changedInput schema / properties / position_y / description
      Previous value: -"Vertical position"New value: +"Vertical position in sequence pixels"
    • 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."
  3. Changed1 schema field changedv1.18.0
    • changedInput schema / properties / speed / description
      Previous value: -"Unsupported by Premiere's public scripting APIs. Supplying this returns an actionable error without mutating the clip."New value: +"Unsupported by Premiere's documented scripting APIs. Supplying this returns an actionable error without mutating the clip; use set_clip_duration to change timeline length."
  4. Changed2 schema fields changedv1.14.4
    • 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"
+}
  5. Changed1 schema field changedv1.11.5
    • 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."
  6. Changed1 schema field changedv1.4.0
    • removedInput schema / additionalProperties
      Removed value: -false
  7. First observedv1.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare the safety profile (non-readonly, non-destructive, non-idempotent), so the bar is lower. The description adds real behavioral context: it discloses a read-back of each requested value, and that speed 'fails before mutation' (i.e. no partial write), which is valuable for error/recovery reasoning.

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?

Two sentences, zero padding, front-loaded with the supported capability before the unsupported case and its alternative. Every clause earns its place.

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 explained, and the 7-param schema is fully documented. The only missing piece is disambiguation against the single-property setter siblings, which slightly limits completeness.

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% and the speed parameter's unsupported note is already in the schema, giving a baseline of 3. The description reinforces the supported-property set and the failure semantics for speed, adding marginal meaning beyond the schema.

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?

States a specific verb (Set) plus the exact resource and enumerates the supported property set (opacity, scale, position, rotation). An agent immediately knows this is a multi-property mutation on a clip, distinct from single-property or duration tools.

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 handles the speed edge case and routes to set_clip_duration. However, it never addresses the granular siblings set_clip_scale, set_clip_opacity, set_clip_rotation, and set_clip_position, so the agent cannot tell from the description whether to batch here or call those instead.

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

Deploy Server

Other Tools