Premiere Pro MCP Server

List Extensions

list_extensions

Read-onlyIdempotent

Lists installed CEP extension panels in Premiere Pro with their id, name, window type, and isActive flag. Use an id with open_extension to open a panel; isActive does not indicate whether a panel is open.

Instructions

List the CEP extension panels installed in Premiere Pro (id, name, window type, and the isActive flag CEP reports). isActive does not show whether a panel is open: in Premiere 26.3 it stayed false for open panels. Use an id with open_extension. CEP connector only.

Input Schema

Name	Required	Description	Default
`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.

Addedv1.26.0Oct 29, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotent/non-destructive, so the safety profile is covered; the description still adds real context beyond them: the isActive field is unreliable (stayed false for open panels in Premiere 26.3) and the tool is limited to the CEP connector. This prevents a plausible misread of the returned data, which annotations could not convey.

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?

Four short sentences: purpose first, then the field caveat, then the follow-on tool, then the backend constraint. No filler, and the most actionable warning (isActive) is placed early.

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, yet the description still flags the one field an agent would otherwise trust incorrectly, and it states the backend restriction. The only omission is any mention of the optional CEP/project guards, which for a zero-required-param listing tool is a minor gap rather than a blocking one.

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% and both parameters (expected_cep_target, expected_project_path) are fully documented in the schema, so the baseline is 3. The description adds nothing about these optional guard parameters or that the call can be made with zero arguments.

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 ('List the CEP extension panels installed in Premiere Pro') and enumerates the returned fields (id, name, window type, isActive). The 'CEP connector only' scope plus the pointer to open_extension makes it unambiguously distinct from nearby tools.

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 the explicit follow-on action ('Use an id with open_extension') and a hard applicability constraint ('CEP connector only'), which tells an agent when this tool is not usable. It does not name an alternative for discovering non-CEP panels or say when to enumerate extensions at all, so it falls short of full when/when-not routing.

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

Deploy Server