Premiere Pro MCP Server

Set Color Value

set_color_value

Assign RGBA color values to an effect property on a clip, such as tint or fill color, by specifying node, component, and property.

Instructions

Set a color value on an effect property (e.g., tint color, fill color)

Input Schema

TableJSON Schema

Name	Required	Description
`red`	Yes	Red (0-255)
`blue`	Yes	Blue (0-255)
`alpha`	Yes	Alpha (0-255)
`green`	Yes	Green (0-255)
`node_id`	Yes	Node ID of the clip
`property_name`	Yes	Name of the color property
`component_name`	Yes	Name of the component/effect

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

Annotations (readOnlyHint=false) already mark this as a write operation, and the description is consistent with that, disclosing a mutating set of RGB+alpha values. It adds modest context via the effect-property examples but does not disclose preconditions such as whether the effect must already exist on the node or whether the prior color is fully replaced.

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?

A single front-loaded sentence with the verb first, the target object, and parenthetical examples inine — zero wasted words. Every element earns its place.

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?

With 100% schema coverage, an existing output schema, and an accurate operation statement, an ageent can call this tool correctly. The gap is tool-routing context: with the near-identical sibling set_effect_property present, the description should clarify when the color-specific variant is appropriate rather than the general one.

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 the schema already documents all 7 required parameters including the 0-255 ranges for red/green/blue/alpha. The description's tint/fill examples add minor context, but per the baseline rule for >80% coverage, the description does not need to compensate further.

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 uses a specific verb-resource pair ('Set a color value on an effect property') and grounds it with concrete examples ('tint color, fill color'). It is clearly about color-specific effect properties, which implicitly distinguishes it from the broader sibling set_effect_property, though it never explicitly names that alternative.

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 offers no guidance on when to choose this tool over related siblings such as set_effect_property, color_correct, apply_lut, or set_color_label. No exclusions, prerequisites, or context-of-use are provided, so an agent must infer selection solely from the tool name and examples.

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

Deploy Server