premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

Reverse Clip

reverse_clip

Flip a timeline clip's playback direction in Adobe Premiere Pro; if Premiere lacks a scripting API for this edit, the tool returns an unsupported-API result.

Instructions

Unavailable: Premiere does not expose a supported scripting API for reversing a timeline clip's playback direction.

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": "reverse_clip"
  }
}

Input Schema

Name	Required	Description
`node_id`	Yes	Node ID of the clip
`reverse`	No	True to reverse, false for normal (default: true)
`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.

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

A3.5/5.0

Behavior3/5

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

Annotations mark this as a non-destructive, non-idempotent mutation, which would normally imply a real edit. The description usefully corrects that expectation by disclosing the host API limitation, a genuine behavioral fact not encoded in annotations. It stops short of saying what actually happens on invocation (error code, no-op, or message) even though the schema advertises idempotency semantics and an output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, front-loaded with the operative word 'Unavailable:' so the agent cannot miss it. Nothing extraneous is included.

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

Completeness3/5

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

Given a 5-parameter tool with nested reviewed-identity objects and an output schema, the description answers the essential question (it cannot be used) but leaves the failure mode unspecified. For a permanently disabled tool that is probably sufficient, though stating the returned error or message would close the loop.

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%, including detailed per-field docs for node_id, reverse, idempotency_key, and the reviewed-identity guard. The description adds no parameter meaning whatsoever, so the baseline of 3 for a fully documented schema is appropriate.

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 states both the intended capability (reversing a timeline clip's playback direction) and its status (not exposed by Premiere's scripting API). An agent can immediately tell that reverse_clip will not perform any edit, which is the single most important fact for tool selection here.

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?

The 'Unavailable:' prefix effectively tells the agent not to call this tool, which is usable guidance. However, it names no alternative approach or sibling (e.g., a speed/duration manipulation like get_clip_speed or set_clip_duration) and gives no workaround, so the routing decision is left implicit.

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

Deploy Server