Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Validate Export Preset

validate_export_preset

Checks whether an Adobe Media Encoder .epr export preset exists, then queries the active Premiere sequence to determine the output extension it produces.

Instructions

Validate that an Adobe Media Encoder .epr preset exists and ask the active Premiere sequence which output extension it produces

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
preset_pathYesFull path to an Adobe Media Encoder export preset (.epr)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the tool completed successfully.
dataNoTool-specific result data when ok is true.
toolYesThe registered MCP tool name.
errorNoFailure detail when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.14.4
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "description": "Tool-specific result data when ok is true."
+    },
+    "error": {
+      "description": "Failure detail when ok is false.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "Whether the tool completed successfully.",
+      "type": "boolean"
+    },
+    "tool": {
+      "description": "The registered MCP tool name.",
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok",
+    "tool"
+  ],
+  "type": "object"
+}
  2. Addedv1.4.0

TDQS

B3.4/5.0
Behavior3/5

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

The phrase 'validate ... exists and ask' suggests a non-destructive, query-like operation, and it surfaces the dependency on the active Premiere sequence. But annotations provide no readOnlyHint safety signal, and the description does not address failure cases such as a missing preset or no active sequence, leaving some behavioral ambiguity.

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?

The description is a single sentence with no filler and front-loads the primary validation action. It is slightly awkward in the 'ask the active Premiere sequence which output extension it produces' phrasing, so it is not perfectly polished, but it remains appropriately compact.

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?

For a simple one-parameter tool with an output schema, the description covers the two core behaviors and names the active-sequence dependency. Still, it does not clearly state whether the output extension belongs to the preset or the sequence, and it omits explicit preconditions like requiring an open Premiere project or active sequence.

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?

The only parameter, preset_path, is already fully documented in the schema with the same '.epr' and 'Full path' details. The description restates the type of preset but adds no additional meaning beyond the schema, so it earns the baseline for high schema coverage.

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 clearly identifies the tool's action: validate that an Adobe Media Encoder .epr preset exists and determine the output extension via the active Premiere sequence. It is specific enough to be distinguished from siblings like get_export_file_extension or get_encoder_presets, though it does not explicitly name them.

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 usage context is implied rather than explicit: an agent can infer this is for checking an export preset before encoding, and that an active sequence is involved. However, there is no explicit statement of when to use this over alternatives like get_export_file_extension or get_encoder_presets, and no when-not-to-use guidance.

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

Deploy Server

Other Tools