Premiere Pro MCP Server

Manage Media Watch

manage_media_watch

Controls a session-bounded local media-folder watcher: begins monitoring approved file types, checks current state, rescans for new signals, or ends tracking; logs changes without automated imports.

Instructions

Start, inspect, rescan, or stop one session-scoped local media-folder monitor. It records bounded file-change signals and never imports media automatically.

Input Schema

TableJSON Schema

Name	Required	Description
`action`	Yes	Watcher action.
`recursive`	No	Monitor contained subdirectories; defaults to false.
`watch_path`	No	Absolute contained directory to monitor; required for start.
`target_bin_id`	No	Optional proposed Premiere destination-bin ID.
`allowed_extensions`	No	File extensions eligible for proposals; required for start.
`approved_workspace_path`	No	Absolute approved workspace root; required for start.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	Whether the tool completed successfully.
`data`	No	Tool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it.
`tool`	Yes	The registered MCP tool name.
`error`	No	Failure detail when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.18.6Sep 30, 2026

changedOutput schema / properties / data / description

Previous value: -"Tool-specific result data when ok is true."New value: +"Tool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it."

Addedv1.14.9Sep 8, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare it is non-read-only, non-idempotent, non-destructive, and closed-world. The description adds useful behavioral context beyond those hints: the monitor is session-scoped, records bounded file-change signals, and does not automatically import media.

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 are tightly front-loaded: the first states the actions and scope, and the second adds the key behavioral limits. Every sentence earns its place with no 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?

Given that an output schema exists, return-value details are not needed in the description. The description covers purpose, session scope, and key non-import behavior, though it could say more about when to choose this monitor versus related import-preview workflows.

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%, so the schema already documents all six parameters, including action, paths, extensions, and target bin. The description does not add syntax, format, or dependency details beyond what the schema provides.

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 gives specific verbs (Start, inspect, rescan, stop) and a specific resource (session-scoped local media-folder monitor). It also distinguishes the tool from import-oriented siblings by stating it never imports media automatically.

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 action list implies the main usage modes, but there is no explicit when-to-use guidance or comparison to alternatives such as preview_watched_media_import. The statement that it never imports media automatically helps distinguish scope but does not fully route the agent among alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server