Premiere Pro MCP Server

Set Effect Property

set_effect_property

Assign a value to a specific effect property on a clip, supporting scalar, boolean, string, vector, and MOGRT JSON inputs, and verify the readback.

Instructions

Set the value of a specific effect property on a clip. Accepts scalar, boolean, string, array-shaped vector values (for example Motion > Position as [x, y]), and MOGRT JSON objects or strings, and verifies the readback component by component.

Input Schema

TableJSON Schema

Name	Required	Description
`value`	Yes	Value to set. Use a number for scalar properties, an array of numbers for vector properties such as Motion > Position or Anchor Point ([x, y]), a boolean for checkbox properties, the exact JSON string reported for a MOGRT text or graphic parameter, or that same JSON object if the client parsed it.
`node_id`	Yes	Node ID of the clip
`effect_name`	Yes	Display name of the effect (e.g., 'Motion', 'Opacity')
`property_name`	Yes	Display name of the property (e.g., 'Scale', 'Position', 'Opacity')

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.

Changed2 schema fields changedv1.18.6Sep 30, 2026

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

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."

Changed3 schema fields changedv1.16.0Sep 16, 2026

addedInput schema / properties / value / additionalProperties
```
Added value: +true
```

changedInput schema / properties / value / description

Previous value: -"Value to set. Use a number for scalar properties, an array of numbers for vector properties such as Motion > Position or Anchor Point ([x, y]), a boolean for checkbox properties, or the exact JSON string reported for a MOGRT text or graphic parameter."New value: +"Value to set. Use a number for scalar properties, an array of numbers for vector properties such as Motion > Position or Anchor Point ([x, y]), a boolean for checkbox properties, the exact JSON string reported for a MOGRT text or graphic parameter, or that same JSON object if the client parsed it."

changedInput schema / properties / value / type

Previous value: -[
-  "number",
-  "string",
-  "boolean",
-  "array"
-]New value: +[
+  "number",
+  "string",
+  "boolean",
+  "array",
+  "object"
+]

Changed6 schema fields changedv1.14.9Sep 8, 2026

changedInput schema / properties / value / description

Previous value: -"Number or string value to set. Use the exact JSON string reported for a MOGRT text or graphic parameter."New value: +"Value to set. Use a number for scalar properties, an array of numbers for vector properties such as Motion > Position or Anchor Point ([x, y]), a boolean for checkbox properties, or the exact JSON string reported for a MOGRT text or graphic parameter."

addedInput schema / properties / value / items
```
Added value: +{
+  "type": "number"
+}
```
addedInput schema / properties / value / maxItems
```
Added value: +4
```
addedInput schema / properties / value / maxLength
```
Added value: +8192
```
addedInput schema / properties / value / minItems
```
Added value: +1
```

addedInput schema / properties / value / type

Added value: +[
+  "number",
+  "string",
+  "boolean",
+  "array"
+]

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

Changed2 schema fields changedv1.13.0Aug 23, 2026

changedInput schema / properties / value / description

Previous value: -"Value to set"New value: +"Number or string value to set. Use the exact JSON string reported for a MOGRT text or graphic parameter."

removedInput schema / properties / value / type
```
Removed value: -"number"
```

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

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare this is a non-readOnly, non-destructive mutation. The description adds useful behavioral detail by enumerating accepted value shapes and stating that the operation verifies readback component by component. It does not cover permissions, failure modes, or reversibility, so it is not a 5.

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?

The purpose is front-loaded in the first clause, followed by the accepted value shapes and readback verification. The single long sentence is dense but earns its clauses; there is no filler.

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. Annotations cover safety hints, and the description supplies value-shape semantics and readback verification. It omits prerequisites such as the effect already existing on the clip, but is otherwise sufficient for correct invocation.

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 the schema itself already documents all four parameters including the value type details. The description repeats the same scalar/boolean/string/vector/MOGRT JSON information, adding little beyond the structured schema. Baseline 3 is appropriate.

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: setting an effect property value on a clip. It does not explicitly name or differentiate from siblings like get_effect_properties or set_clip_properties, though the scope is clear enough from 'effect property on a clip.'

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 when-to-use guidance, no exclusion conditions, and no alternatives. It only lists accepted value types, which is parameter semantics rather than usage guidance.

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

Deploy Server

Set Effect Property

Instructions

Input Schema

Output Schema

Schema Changelog

TDQS

Other Tools