Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Export As Fcp Xml

export_as_fcp_xml

Export the active Premiere Pro sequence to a Final Cut Pro XML file for cross-platform video editing interoperability.

Instructions

Export the active sequence as a Final Cut Pro XML file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
output_pathYesFull output file path (e.g., '/Users/me/export.xml')

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. Changed1 schema field changedv1.4.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.1.1

TDQS

A3.6/5.0
Behavior2/5

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

No annotations provide meaningful safety context (readOnlyHint=false, idempotentHint=false, destructiveHint=false), so the description carries the burden. It only says 'Export' and does not disclose that a file is written to output_path, whether an existing file may be overwritten, or what happens if no sequence is active. The description adds little behavioral detail beyond the tool name.

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?

One short, front-loaded sentence contains every essential element: action, target, and output format. There is no filler or redundant restatement of the title.

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 single-parameter export tool with a documented schema and an output schema present, the description is nearly complete. The only notable gap is the lack of explicit guidance about when to choose this over other export formats, but the basic invocation requirements are clear.

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%: the single output_path parameter is fully documented with an example. The description adds nothing beyond the schema, which is acceptable given the complete schema coverage, so a baseline score of 3 is appropriate.

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 names a specific verb ('Export'), a clear resource ('the active sequence'), and an unambiguous output format ('Final Cut Pro XML file'). This distinguishes it from related siblings like export_aaf, export_omf, and export_sequence without requiring schema inspection.

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 format 'Final Cut Pro XML' implies when this tool should be used, but the description does not explicitly contrast it with alternatives such as export_aaf, export_omf, or export_sequence. There is no when-not-to-use guidance, only an implicit usage condition.

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