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

premiere-pro-mcp

by MauricePutinas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Import media files

premiere_import_files

Import media files (video, audio, images) into an open Premiere Pro project, optionally into a specific bin for organization.

Instructions

Import one or more media files (video/audio/image) into the open project, optionally into a named bin. All paths must exist. Warning dialogs are suppressed by default.

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": {
      "paths": "<paths>"
    },
    "name": "premiere_import_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathsYesAbsolute paths of media files to import.
binNameNoName of an existing bin to import into (defaults to the project root).
importAsNumberedStillsNoTreat a numbered image sequence as a single still clip.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

The description reveals that warning dialogs are suppressed by default, a behavioral trait beyond the openWorldHint annotation. It also states required preconditions (paths must exist) but does not detail error handling or return behavior, which is a minor gap.

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?

The description is extremely concise (two sentences, 28 words) and front-loads the primary purpose in the first sentence. Every clause contributes value with no redundancy or filler.

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 simple import tool with three parameters and no output schema, the description covers the main action, media types, optional bin, path existence precondition, and a behavioral quirk (warning suppression). It lacks explicit return value info but is otherwise fairly 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?

The input schema already provides full descriptions for all three parameters (100% coverage). The description adds context about 'optionally into a named bin' and 'All paths must exist' but does not significantly enhance the parameter meaning beyond the schema.

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 clearly states the tool imports one or more media files into the open project, optionally into a named bin. It specifies media types (video/audio/image) and distinguishes from sibling tools like premiere_add_audio or premiere_add_effect, which are not import operations.

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 description implies the tool is used for importing media files but does not explicitly provide when-to-use or when-not-to-use guidance. It mentions preconditions (paths must exist) but no alternatives, making it adequate but not exemplary.

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