premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

List export presets

premiere_list_export_presets

Read-only

List available .epr export presets (H.264, HEVC, ProRes, AAC, etc.) filtered by query, returning paths for use in export sequences.

Instructions

List available .epr export presets found on disk (H.264/HEVC/ProRes/AAC etc.), optionally filtered by a name query. Pass one of these 'path' values to premiere_export_sequence. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "premiere_list_export_presets"
  }
}

Input Schema

Name	Required	Description	Default
`query`	No	Filter presets by filename substring (e.g. 'H264', 'ProRes', '1080').
`limit`	No	Max presets to return (default 80).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 21, 2026

TDQS

A4.4/5.0

Behavior5/5

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

The description declares the tool is 'Read-only', aligning with the readOnlyHint annotation. It adds context about finding presets on disk and listing available formats, which goes beyond the annotation to inform the agent about side effects and behavior.

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?

The description is extremely concise with two sentences. The first sentence delivers the core purpose and filtering capability, while the second provides a usage hint and safety note. No redundant words.

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?

Given the simple tool (2 optional params, no output schema), the description adequately covers purpose, filtering, and output usage. However, it does not specify the output format (e.g., list of objects with 'path'), which could be helpful. Still, it's sufficient for an agent to use correctly.

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 the baseline is 3. The description mentions 'optionally filtered by a name query', which adds no new information beyond the schema's parameter descriptions for 'query' and 'limit'.

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?

The description clearly states the tool lists .epr export presets from disk, specifying codec types (H.264/HEVC/ProRes/AAC) and optional filtering. It distinguishes from sibling 'premiere_list_sequence_presets' by focusing on export presets.

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?

The description explicitly tells the agent to pass the returned 'path' value to 'premiere_export_sequence', providing a clear usage context. It does not explicitly state when to avoid this tool, but the purpose is narrow enough that no exclusion is needed.

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

Deploy Server