premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

Set Effect Property

set_effect_property

Sets one effect property value on a Premiere Pro clip, including Motion, Opacity, audio parameters and MOGRT text, then verifies the write via readback so unapplied values are never reported as applied.

Instructions

Set one effect property. Duplicate names require property_index from get_effect_properties. Colour values use [alpha, red, green, blue] and the lossless colour API; keyframed writes are refused. Readback reports verified, failed or committed_unverified; unreadable values are never reported as applied. Audio effect parameters (effects on audio clips other than built-in Volume, Channel Volume, Panner and Balance) take Premiere's normalized 0-1 value, not Hz, dB or ms; a number outside 0-1 is refused before the write when the current value is inside 0-1, unless allow_out_of_range_audio_value is true. valueScale describes the returned value; requestedValueScale is added when the request was on a different scale. Calibrate audio changes by rendering.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "node_id": "<node_id>",
      "effect_name": "<effect_name>",
      "property_name": "<property_name>",
      "value": "<value>"
    },
    "name": "set_effect_property"
  }
}

Input Schema

Name	Required	Description
`value`	Yes	Value to set. Use a number for scalar properties (for audio effects, the normalized 0-1 value get_effect_properties reports, not Hz, dB or ms), 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; duplicate names require property_index.
`property_index`	No	Optional property index from get_effect_properties; required when property_name is duplicated.
`idempotency_key`	No	Optional client-chosen key (1-128 chars of A-Z a-z 0-9 . _ : -) for this intended edit. Pass a fresh key per edit and reuse it only when retrying that same edit, for example after a client-side timeout. A repeat with the same tool, key and arguments is not run again: while the first call is running it fails with IDEMPOTENCY_IN_PROGRESS (poll get_last_operations); after it finished it returns the original outcome marked replayed. A definite failure with nothing applied (receipt outcome not_applied) may be retried with the same key. Reusing a key with different arguments fails with IDEMPOTENCY_KEY_REUSED. Scoped to this MCP session (the stdio server process, or the HTTP server process when Streamable HTTP is stateless per request) and held in memory only (200 keys, 1 hour); it does not survive a restart or reconnect. Read-only invocations are never deduplicated.
`expected_cep_target`	No	Optional reviewed CEP sequence/clip identity and exact tick ranges. Checked before every generated command; UXP refuses this CEP-only guard.
`expected_project_path`	No	Optional absolute saved-project path. Every generated CEP command refuses before its body when the active project differs or is unsaved. UXP commands refuse this CEP-only guard; local-only tools do not inspect Premiere. Omit to keep existing behavior.
`allow_out_of_range_audio_value`	No	Default false. Audio effect parameters normally use normalized 0-1 values, so a number outside 0-1 (for example 80 meant as Hz) is refused before the write while the current value is inside 0-1. Set true only when this parameter is known to accept that raw value.

Output 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.
`receipt`	No	Versioned common mutation receipt; success never implies rendered verification.
`idempotency`	No	Present when idempotency_key deduplicated this call: replayed is true when the original outcome was returned instead of running again.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.30.0Nov 14, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Beyond the annotations, it discloses that keyframed writes are refused, that colours go through a lossless colour API, that readback reports verified/failed/committed_unverified and never claims unapplied values, and that out-of-range audio numbers are rejected before the write. These are exactly the mutation-safety behaviors an agent cannot infer from readOnlyHint=false or destructiveHint=false.

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 core action and the duplicate-name rule are front-loaded, and each subsequent sentence carries a distinct constraint (colour format, keyframe refusal, verification outcomes, audio scaling). It is dense and slightly run-on, with the audio clause packed into a single long sentence, but no sentence is 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?

For a 9-parameter mutation tool with a nested identity guard and an output schema, the description covers the risky parts an agent must get right: property disambiguation, colour encoding, audio normalization, and refusal behavior. Idempotency and the CEP/project-path guards are left to schema descriptions, which is acceptable given their thorough in-schema documentation.

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; the description still adds meaning the schema lacks, notably the [alpha, red, green, blue] ordering for colour values and the normalized 0-1 rule for audio effect parameters. It does not explain idempotency_key, expected_cep_target or expected_project_path semantics, leaving that entirely to the schema.

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 first sentence states a specific verb and resource ('Set one effect property'), scoping it to a single property rather than a batch, which implicitly separates it from siblings like set_clip_properties. It also points to get_effect_properties as the source of property_index, but it never explicitly names an alternative for when a bulk write is preferable.

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?

It gives concrete conditional guidance: use property_index when names are duplicated, pass allow_out_of_range_audio_value only when the parameter is known to accept raw values, and render to calibrate audio changes. It also states a hard exclusion ('keyframed writes are refused'), though it does not name which sibling to use instead for keyframes.

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

Deploy Server