Skip to main content
Glama
Sign In
premiere-pro-mcp

premiere-pro-mcp

by matt-j-penny
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get Effect Properties

get_effect_properties
Read-onlyIdempotent

Lists all properties and current values for a specified effect on a clip, including value scales and warnings for audio parameter units.

Instructions

List all properties of a specific effect on a clip, including current values. Values are what Premiere's scripting API returns, not necessarily the units shown in Effect Controls. Effects on audio clips (anything other than the built-in Volume, Channel Volume, Panner and Balance) usually use normalized 0-1 values. Each numeric property reports valueScale (normalized_0_1 or host_raw_unknown), parameterScale summarises the values seen (normalized_0_1, host_raw_unknown, mixed or unknown), and the result carries a warning, because Adobe does not document the mapping to Hz, dB or ms. Calibrate audio effect changes by rendering. Volume > Level also reports displayValue in dB.

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>"
    },
    "name": "get_effect_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_idYesNode ID of the clip
effect_nameYesDisplay name of the effect (e.g., 'Motion', 'Opacity', 'Lumetri Color')
expected_cep_targetNoOptional reviewed CEP sequence/clip identity and exact tick ranges. Checked before every generated command; UXP refuses this CEP-only guard.
expected_project_pathNoOptional 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.

Output 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.
receiptNoVersioned common mutation receipt; success never implies rendered verification.
idempotencyNoPresent 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.

  1. First observedv1.30.0

TDQS

A3.9/5.0
Behavior5/5

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

Goes well beyond the annotations: it warns that returned values are host-scripting values, not the units seen in Effect Controls, that most audio effects are normalized 0-1, that valueScale/parameterScale are reported, that a warning accompanies the result because Adobe does not document the Hz/dB/ms mapping, and that Volume > Level alone reports displayValue in dB. These are non-obvious behavioral facts an agent could not get from readOnlyHint/destructiveHint or the schema, and they directly affect how the returned numbers should be interpreted.

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-loaded with the core action in the first clause, then progressively adds interpretation caveats. It is dense and slightly repetitive around the scale taxonomies (valueScale and parameterScale are enumerated twice in effect), but every sentence carries actionable meaning.

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-shape documentation is not required, yet the description still supplies the crucial semantic layer about what those values mean. Annotations cover safety and idempotency. The remaining gap is the absence of any note on the two optional guard parameters and when to use them, which for a tool with a nested identity-guard object is a real omission.

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 node_id, effect_name, and the guard objects. The description adds no parameter-level guidance of its own — it never mentions node_id, effect_name format, or when to supply expected_cep_target/expected_project_path. Baseline 3 is appropriate since the schema carries this load.

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?

Opens with a specific verb and resource: 'List all properties of a specific effect on a clip, including current values.' An agent immediately knows this is a read of effect-level properties rather than clip-level properties. It does not explicitly distinguish itself from nearby siblings like list_clip_effects or get_clip_properties, so the differentiation is inferable rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: it reads current values, and 'Calibrate audio effect changes by rendering' hints at the read-before/after workflow with set_effect_property. There is no explicit 'use this when X, use that when Y' routing, and no prerequisites or preconditions are given.

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