Skip to main content
Glama
Sign In
premiere-pro-mcp

premiere-pro-mcp

by MauricePutinas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Inspect project file

premiere_inspect_project_file
Read-only

Inspect a Premiere Pro project file (.prproj) without opening the application: decompress the gzipped XML to reveal file size, metadata, and approximate counts of sequences, media, and clips. Read-only analysis.

Instructions

Inspect a .prproj WITHOUT opening Premiere: decompress the gzipped XML and report file size, decompressed size, project metadata and approximate counts of sequences/media/clips. Read-only.

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": {
      "path": "<path>"
    },
    "name": "premiere_inspect_project_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute path to a .prproj file.
includeHeadNoInclude the first 2 KB of decompressed XML.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already provide readOnlyHint=true, and the description reinforces 'Read-only'. It adds details about decompression and reported fields, which are valuable beyond annotations.

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 with no wasted words. The key point ('WITHOUT opening Premiere') is front-loaded, and every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, but the description sufficiently explains what the tool returns. Given the low complexity (2 params, 1 required) and the clear read-only context, the description is complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description adds context about the tool's output (file size, decompressed size, etc.), which helps infer parameter purpose beyond the schema descriptions.

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 explicitly states 'Inspect a .prproj WITHOUT opening Premiere' and lists specific reports (file size, decompressed size, metadata, counts). It clearly distinguishes from sibling tools that open or modify projects.

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 indicates read-only inspection without launching Premiere, implying when to use it. While it doesn't name alternatives, the context of sibling tools makes it clear.

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