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

premiere-pro-mcp

by MauricePutinas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Save project as

premiere_save_project_as

Save the currently open Adobe Premiere Pro project to a new file path. Automatically backs up existing files and requires confirmation when overwriting.

Instructions

Save the open project to a new path. If the target exists it is gated behind confirm:true and backed up first. Path must be inside an allowed working root.

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_save_project_as"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute destination path (.prproj added if missing).
confirmNoRequired only if the target already exists.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations indicate non-destructive (destructiveHint: false). Description adds that existing targets are backed up and gated behind confirm, providing extra safety context. No mention of potential side effects like closing current project, but adequate for the operation.

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 efficient sentences: first states purpose, second details conditions. No redundant words, all information earn 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 2 parameters, no output schema, and annotations present, description covers key behaviors (backup, confirm gate, path constraint). Lacks explicit mention of return value, but sufficient for the tool's simplicity.

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?

Input schema already covers both parameters with clear descriptions (path: absolute with .prproj append; confirm: required only if target exists). Description adds no further semantic detail beyond schema, earning baseline score.

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?

Description clearly states 'Save the open project to a new path,' specifying the verb (save), resource (project), and unique behavior (new path). Distinguished from siblings like 'premiere_save_project' which saves to current path, and 'premiere_backup_project' which is a different operation.

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?

Provides context on when confirm is needed and path constraints (inside allowed root). Does not explicitly contrast with alternative save tools or state when not to use this tool, though the sibling list implies differentiation.

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