Skip to main content
Glama

Set Clip Properties

set_clip_properties

Set a clip's opacity, scale, position, and rotation in Premiere Pro, then read back requested values; speed is unsupported—use duration editing to change timeline length.

Instructions

Set supported clip properties (opacity, scale, position, rotation) and read each requested value back. Position uses pixels by default or explicit normalized 0–1 fractions; an omitted-unit 0–1 pair retains pixels with a warning. Clip speed is unsupported and fails before mutation; use set_clip_duration to change a clip's timeline length.

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

Input Schema

NameRequiredDescriptionDefault
scaleNoScale percentage (0-10000; 100 = original size)
speedNoUnsupported by Premiere's documented scripting APIs. Supplying this returns an actionable error without mutating the clip; use set_clip_duration to change timeline length.
unitsNoPosition units; pixels by default or normalized 0–1 sequence-frame fractions. Requires a position value.
node_idYesNode ID of the clip
opacityNoOpacity value (0-100)
rotationNoRotation in degrees
position_xNoHorizontal position in the selected units: sequence pixels by default or normalized 0–1 fractions.
position_yNoVertical position in the selected units: sequence pixels by default or normalized 0–1 fractions.
idempotency_keyNoOptional 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_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.7/5.0
Behavior4/5

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

Annotations already cover safety (non-destructive, not read-only, mutating) so the description is not obligated to restate them, and it instead adds genuinely new behavior: unsupported input fails before any mutation (atomicity), each requested value is read back after the edit, and an omitted-unit 0-1 pair is interpreted as pixels with a warning rather than an error. It does not discuss the idempotency/replay semantics, but those are fully documented in the schema.

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?

Three sentences, front-loaded with what is supported, then unit semantics, then the failure/alternative. No filler. The middle sentence about the omitted-unit pair is slightly dense but it encodes a real trap that saves a round trip.

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 an 11-parameter mutation tool with nested guard objects and an output schema, the description covers the semantics an agent actually needs to avoid a bad call (units, unsupported speed, read-back) and leaves guard/idempotency detail to the schema, which documents it thoroughly. The only missing piece is routing versus the single-property siblings.

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 coverage is 100%, so the schema already defines every parameter, and the description's main contribution is the units default and the omitted-unit 0-1 pitfall, which does go beyond the schema text. Otherwise it stays at the conceptual level and does not add per-parameter detail beyond what the schema supplies.

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 opens with a specific verb and resource and enumerates exactly which properties it touches (opacity, scale, position, rotation), plus it explicitly excludes speed. It does not, however, distinguish itself from the granular per-property siblings (set_clip_opacity, set_clip_scale, set_clip_position, set_clip_rotation), so an agent must still infer why the composite tool exists.

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?

There is real when-not guidance: speed is unsupported and set_clip_duration is named as the alternative for timeline length. But there is no guidance on when to choose this composite tool over the single-property siblings, which is the main selection ambiguity an agent faces here.

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