premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

Inspect Otio Interchange

inspect_otio_interchange

Read-onlyIdempotent

Parse a local OTIO timeline into exact-tick offline tracks, clips, gaps, and transitions, and report missing media, opaque nests, and unsupported timing without importing a project.

Instructions

Parse a bounded local OTIO Timeline.1 into exact-tick offline tracks/clips/gaps/transitions. Reports missing media, opaque nests/effects/metadata and unsupported timing. Synthetic IDs never authorize Premiere writes; this tool never imports a project.

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": {
      "path": "<path>"
    },
    "name": "inspect_otio_interchange"
  }
}

Input Schema

Name	Required	Description
`path`	Yes	Absolute caller-selected local file path. Referenced media is never opened automatically.
`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.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description still adds real behavior beyond that: it works offline (never opens referenced media), it surfaces missing media and opaque nests/effects/metadata, it flags unsupported timing, and its synthetic IDs are explicitly barred from authorizing writes. Return format/pagination details are left to the 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.

Conciseness4/5

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

Three sentences, front-loaded with what is parsed and what is emitted, followed by reporting coverage and the write-safety boundary. Dense and mostly waste-free, though the phrase "opaque nests/effects/metadata" is compressed jargon that costs a little readability.

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 read-only local parser with a full output schema, the description covers the essentials: scope, offline behavior, emitted element types, limitation reporting, and the no-import/no-write guarantee. Nothing an agent needs in order to call it correctly is missing, though it could have noted that the CEP guard parameters are irrelevant to this local-only tool.

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% across all four parameters, including a lengthy idempotency_key explanation and the expected_cep_target guard structure, so the schema does the heavy lifting. The description only hints at the path constraint via "bounded local" and adds nothing about the CEP guard or idempotency parameters, so the baseline 3 is correct.

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?

"Parse a bounded local OTIO Timeline.1 into exact-tick offline tracks/clips/gaps/transitions" gives a specific verb, a specific resource format, and the shape of the result, which lets an agent distinguish it from the FCPXML/EDL inspection siblings by format alone. It stops short of naming an alternative sibling explicitly, so it lands at clear-but-not-routing.

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?

"bounded local" plus "this tool never imports a project" and "Synthetic IDs never authorize Premiere writes" set a clear usage boundary: read-only inspection of a local OTIO file, not an import path. It does not explicitly say when to choose this over inspect_fcpxml_interchange or inspect_interchange_loss_report, so the alternative-selection guidance is implied rather than stated.

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

Deploy Server