Premiere Pro MCP Server

Ripple Remove Timeline Ranges

ripple_remove_timeline_ranges

Preview or apply a single-pass ripple removal for up to 50 sorted, non-overlapping timeline ranges on unlocked sync-locked tracks, then delete clips inside those ranges.

Instructions

Refuses attached transitions or unreadable transition collections before structural edits; inspect transitionsAffected and use remove_transition first. Preview or apply a single-pass ripple removal for up to 50 sorted, non-overlapping timeline ranges on all unlocked, sync-locked tracks. Requires a preview confirmation token to apply. Integer frame rates only. The preview returns per-track counts and at most 50 planned-clip samples; clips fully inside ranges are removed. Kept pieces cut from one linked audio/video clip are relinked and read back after the move. Large edits need allow_large_ripple: true.

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": {
      "ranges": "<ranges>",
      "scope": "<scope>",
      "range_content": "<range_content>"
    },
    "name": "ripple_remove_timeline_ranges"
  }
}

Input Schema

Name	Required	Description
`scope`	Yes	All participating tracks must be sync-locked and unlocked.
`ranges`	Yes	Sorted, non-overlapping timeline intervals to remove.
`dry_run`	No	Return bounded read-only counts and up to 50 plan samples; default true.
`batch_size`	No	QE calls per bridge command (default: PREMIERE_MCP_QE_BATCH_SIZE or 8; clamped to 1-32).
`sequence_id`	No	Sequence name or ID; defaults to the active sequence. It must be the active sequence, because the edit runs through QE; another sequence is refused without changes.
`range_content`	Yes	Delete clips fully inside each removed range.
`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.
`allow_large_ripple`	No	Required when more than 400 clips will move.
`confirmation_token`	No	Single-use token from a successful dry run; required to apply.
`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.

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.

Changed1 schema field changedv1.30.0Nov 9, 2026

changedInput schema / properties / idempotency_key / description

Previous value: -"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 one HTTP session) and held in memory only (200 keys, 1 hour); it does not survive a restart or reconnect. Read-only invocations are never deduplicated."New value: +"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."

Changed1 schema field changedv1.28.0Nov 2, 2026

addedInput schema / properties / batch_size

Added value: +{
+  "description": "QE calls per bridge command (default: PREMIERE_MCP_QE_BATCH_SIZE or 8; clamped to 1-32).",
+  "maximum": 32,
+  "minimum": 1,
+  "type": "number"
+}

Changed2 schema fields changedv1.25.0Oct 24, 2026

addedInput schema / properties / idempotency_key

Added value: +{
+  "description": "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 one HTTP session) and held in memory only (200 keys, 1 hour); it does not survive a restart or reconnect. Read-only invocations are never deduplicated.",
+  "maxLength": 128,
+  "minLength": 1,
+  "pattern": "^[A-Za-z0-9._:-]+$",
+  "type": "string"
+}

addedOutput schema / properties / idempotency

Added value: +{
+  "additionalProperties": true,
+  "description": "Present when idempotency_key deduplicated this call: replayed is true when the original outcome was returned instead of running again.",
+  "type": "object"
+}

Changed1 schema field changedv1.24.1Oct 17, 2026

changedInput schema / properties / sequence_id / description

Previous value: -"Sequence name or ID; defaults to active sequence."New value: +"Sequence name or ID; defaults to the active sequence. It must be the active sequence, because the edit runs through QE; another sequence is refused without changes."

Addedv1.24.0Oct 12, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With annotations supplied, the bar is lower, and the description still adds real behavior: refusal conditions, integer-frame-rate-only restriction, per-track counts and at most 50 planned-clip samples in preview, and relinking/read-back of kept pieces from linked A/V clips. One caveat: destructiveHint=false sits awkwardly beside 'clips fully inside ranges are removed' — the description is the more accurate of the two, but the mismatch means an agent cannot fully trust the annotation's safety signal.

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?

Dense and waste-free at six short sentences, each carrying a distinct constraint (refusal, scope, token, frame rate, preview output, relinking, large-edit gate). The ordering is slightly off: it opens with the transition-refusal edge case before stating the core purpose, so the headline capability is not truly front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter, nested-schema, high-risk edit tool with an output schema, the description covers the parts structure cannot: preconditions and refusals, required preview/confirmation flow, hard limits (50 ranges, 400 clips), and post-edit relinking guarantees. Nothing essential to calling it correctly appears to be missing.

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 every parameter including idempotency_key, confirmation_token, and batch_size is already documented in the schema. The description restates the confirmation-token requirement and the allow_large_ripple trigger and adds the 'integer frame rates only' constraint, but adds little parameter meaning beyond what the schema already carries, so baseline 3 applies.

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: 'single-pass ripple removal for up to 50 sorted, non-overlapping timeline ranges on all unlocked, sync-locked tracks.' It also names the operation's scope (preview vs apply) so an agent can distinguish it from remove_transition and simpler removals without opening the schema.

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 an explicit precondition-and-alternative: 'Refuses attached transitions ... inspect transitionsAffected and use remove_transition first,' plus the required preview-then-apply sequence and the 'allow_large_ripple: true' trigger for large edits. It does not explicitly say when to prefer this over ripple_delete or remove_from_timeline, so routing among the other removal siblings is left to inference.

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

Deploy Server