Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Set Clip Position

set_clip_position

Set a video clip's Motion Position in pixels with English or measured Spanish built-in names. Then read the value back.

Instructions

Set the Position property on a video clip's Motion effect using English or measured Spanish built-in names, then read it back. Values are in pixels.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYesX position in sequence pixels (converted to Premiere's normalized Position when the host stores it that way)
yYesY position in sequence pixels (converted to Premiere's normalized Position when the host stores it that way)
node_idYesNode ID of the clip

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. Changed4 schema fields changedv1.18.6
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / x / description
      Previous value: -"X position in pixels"New value: +"X position in sequence pixels (converted to Premiere's normalized Position when the host stores it that way)"
    • changedInput schema / properties / y / description
      Previous value: -"Y position in pixels"New value: +"Y position in sequence pixels (converted to Premiere's normalized Position when the host stores it that way)"
    • 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."
  2. 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"
+}
  3. Changed1 schema field changedv1.4.0
    • removedInput schema / additionalProperties
      Removed value: -false
  4. First observedv1.1.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false), so the mutation nature is covered. The description adds useful context by disclosing that the tool reads the value back after setting and that values are in pixels, but it omits auth requirements and what happens on failure or to unmentioned Position axes.

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?

Two short sentences with the action front-loaded. The clause about 'English or measured Spanish built-in names' is somewhat cryptic and costs a little clarity, but the overall size is appropriate and wastes little space.

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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. However, for a mutation tool with no when-to-use guidance and an unexplained naming convention, the description leaves gaps an agent would need to call it confidently.

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 x, y and node_id are fully documented in the schema. The description's 'Values are in pixels' merely repeats the schema's 'X position in sequence pixels' and adds no syntax, range, or coordinate-origin detail beyond it, so the baseline 3 applies.

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 the Position property on a video clip's Motion effect'), clearly distinguishing it from sibling setters like set_clip_scale, set_clip_rotation and set_clip_opacity. It does not explicitly name those siblings, but the resource is precise enough for an agent to route correctly.

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?

There is no when-to-use guidance and no alternatives named. An agent is left to infer that this is the tool for positioning versus set_clip_anchor_point or set_effect_property. The phrase 'using English or measured Spanish built-in names' hints at a naming convention but never explains what that means operationally.

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