premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

Get Export File Extension

get_export_file_extension

Read-onlyIdempotent

Retrieve the export file extension from Premiere for a preset path; if missing, infer it only for an existing .epr in a recognized Adobe Media Encoder folder and report the resolved path.

Instructions

Get the export file extension from Premiere. If Premiere returns none, infer it only for an existing .epr whose real filesystem parent is a recognized Adobe Media Encoder format folder; report that resolved preset path. This fallback is unconfirmed and should be checked before delivery.

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": {
      "preset_path": "<preset_path>"
    },
    "name": "get_export_file_extension"
  }
}

Input Schema

Name	Required	Description
`preset_path`	Yes	Absolute path on this server to the export preset file (.epr). Relative paths, NUL bytes and trailing directory separators are refused before host dispatch.
`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.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive/openWorld=false, so the safety profile is covered. The description adds real behavioral context beyond that: an undocumented inference fallback, the filesystem condition that gates it, that the resolved preset path is reported, and an explicit reliability caveat ('unconfirmed and should be checked before delivery'). That caveat is exactly the kind of trait an agent needs and cannot get from structured fields.

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 the primary behavior followed by the conditional fallback and its caveat. No filler; each sentence contributes a distinct fact. Slightly dense phrasing in the second sentence but nothing extraneous.

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, so return-value explanation is unnecessary, and the parameter surface is fully documented in the schema. The description completes the picture by covering the non-obvious fallback and its trust level. Minor gap: it does not say what happens when no extension can be resolved at all and no preset path exists.

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% across all four parameters, including the .epr path constraint and the detailed idempotency_key semantics, so the schema carries the parameter burden. The description echoes the .epr requirement but adds no format or meaning beyond what the schema states; baseline 3 applies.

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 names a specific verb and resource — retrieving the export file extension from Premiere — and adds a precise fallback rule (infer only for an existing .epr whose real parent is a recognized Adobe Media Encoder format folder). An agent can tell what it returns without opening the schema. It does not name a sibling such as validate_export_preset, so it falls short of the top band.

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?

Usage is implied through the fallback condition: the inference path applies only to an existing .epr under a recognized AME format folder, otherwise the host value is used. There is no explicit statement of when to call this tool versus alternatives like validate_export_preset, and no preconditions for the primary (non-fallback) path.

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

Deploy Server