Skip to main content
Glama
Sign In
MCP Premiere Pro

MCP Premiere Pro

by Miinwan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

sync_color_layers

Copies all Lumetri Color parameters from a master color layer to every matching 'Màu ' layer, keeping same-scene instances identical after grading; other source groups remain untouched.

Instructions

Make every colour layer of the same scene identical again after grading one of them: for each "Màu " name, copies ALL Lumetri Color parameters (basic, creative, curves, wheels, HSL, vignette) from the master instance to the other instances of that name. master: a clip name + index or the instance under the playhead; default the first instance of each name. Different sources are never touched by each other.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sync_color_layers"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOnly this layer name, e.g. "Màu A001_C0661" (default every "Màu …" group)
sequenceIdNoSequence ID (GUID).
fromPlayheadNoUse the instance under the playhead as the master for its group (default false: the first instance)
sequenceNameNoSequence name. Default: the active sequence.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description does the heavy lifting: it discloses that ALL Lumetri Color parameter groups are copied onto other instances, meaning existing grading on those layers is overwritten, and adds the safety rule that different sources never affect each other. It omits failure modes (missing master, no matching name) and permission requirements, leaving some behavioral gaps.

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?

Front-loads the core action (make colour layers identical again after grading one) and then supplies the necessary copy scope, master rules, and isolation guarantee. It is dense but each sentence contributes; minor structural improvement possible.

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?

Given no annotations and no output schema, the description covers purpose, exact copied parameters, master-selection logic, defaults, and source isolation. It leaves return/result behavior and error conditions unstated, which is a modest gap for a mutation tool.

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 baseline is 3, but the description adds meaningful master-selection semantics: "a clip name + index or the instance under the playhead; default the first instance of each name." This clarifies how name and fromPlayhead interact beyond the schema field text.

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 and resource: makes colour layers identical by copying all Lumetri Color parameters between instances of the same "Màu <source>" name. It clearly distinguishes from generic effect-copy siblings by naming the exact scope (same-name layers within a scene).

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?

Gives a clear trigger — use it "after grading one of them" — and explains the default master-selection behavior. It does not explicitly name alternatives like copy_effect_values or copy_effects_between_clips, so a 4 rather than 5.

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