Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Preview Project Intake

preview_project_intake
Read-onlyIdempotent

Audits a Premiere project against a facility intake template, returning a path-redacted report and a non-mutating organization proposal without changing the project or saving the template.

Instructions

Inspect a bounded Premiere project against an explicit facility intake template and return a path-redacted report plus a non-mutating organization proposal. It never changes Premiere or persists the template.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
templateYesVersioned facility policy. Unknown fields and unsafe matching expressions are rejected by the intake engine.
max_itemsNoMaximum project items to inspect; defaults to 2000. Truncation returns an incomplete report.
include_pathsNoInclude observed media paths in findings. Defaults to false; hashes are returned instead.

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. Changed6 schema fields changedv1.14.9
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / max_items / maximum
      Added value: +2000
    • addedInput schema / properties / max_items / minimum
      Added value: +1
    • addedInput schema / properties / max_items / type
      Added value: +"integer"
    • removedInput schema / properties / template / additionalProperties
      Removed value: -{}
    • removedInput schema / properties / template / propertyNames
      Removed value: -{
-  "type": "string"
-}
  2. 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"
+}
  3. Addedv1.13.0

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already mark readOnly, idempotent, and non-destructive, but the description adds genuine behavioral detail: it 'never changes Premiere or persists the template', returns path-redacted findings, and is bounded by max_items truncation. This is exactly the safety and side-effect context that helps an agent trust a preview call.

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?

Two sentences, no filler, with the core action and return deliverables front-loaded and the safety guarantee immediately after. Every phrase earns its place.

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?

With a full output schema, detailed parameter descriptions, and safety annotations, the description covers the operation's purpose, non-mutation, path redaction, and boundedness. A slightly more explicit statement of when this preview should be preferred over mutating intake workflows would make it fully complete.

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 each parameter (template, max_items, include_paths) already has a meaningful description. The tool description adds context like 'path-redacted' but does not need to repeat parameter syntax; the schema carries the burden adequately.

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 opens with a specific verb ('Inspect') and resource ('a bounded Premiere project ... against an explicit facility intake template'), then states the two concrete deliverables: a path-redacted report and a non-mutating organization proposal. This clearly differentiates it from generic preview_* siblings by anchoring it to facility intake templates.

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 context is clear: use this when inspecting a project against an intake template and wanting a preview that does not mutate. However, it never names an alternative tool or states when-not-to-use it, so the agent must infer the appropriate selection from the template-oriented wording.

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