Premiere Pro MCP Server

Detect Motion Peaks

detect_motion_peaks

Find probable high-motion moments in a bounded local video sample by measuring decoded frame differences; returns read-only editorial candidates for review.

Instructions

Find probable high-motion moments in a bounded local video sample from decoded frame differences. Read-only editorial candidates; camera movement, flashes, cuts, and subject motion are not semantically distinguished.

Input Schema

TableJSON Schema

Name	Required	Description
`threshold`	No	Minimum mean luma-frame difference from 0 through 255 (default: 12)
`media_path`	Yes	Existing local video file
`maximum_events`	No	Maximum returned candidates from 1 through 1000 (default: 200)
`sample_seconds`	No	Decode duration from 1 through 300 seconds (default: 60)
`samples_per_second`	No	Frame samples per second from 1 through 10 (default: 4)
`minimum_interval_seconds`	No	Minimum peak spacing from 0.1 through 30 seconds (default: 1)

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.

Changed2 schema fields changedv1.18.6Sep 30, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

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."

Changed1 schema field changedv1.14.9Sep 8, 2026
- addedInput schema / properties / maximum_events / type
```
Added value: +"integer"
```
Addedv1.14.5Sep 1, 2026

TDQS

C2.9/5.0

Behavior1/5

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

Description calls the tool 'read-only' while annotations set readOnlyHint=false, a direct contradiction. This is a serious inconsistency that could mislead the agent about whether the operation mutates state; per rubric, score 1 and flag contradiction.

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, front-loaded with purpose and followed by essential caveats. Every clause earns its place, and there is no filler.

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

Completeness3/5

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

Output schema exists, so return values need not be explained. However, the description's 'read-only' claim conflicts with annotations, and it provides no routing among many similar detection/analysis siblings; the resulting ambiguity leaves it minimally viable.

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 fully documents all six parameters. The description adds no parameter-specific detail beyond 'bounded local video sample,' which loosely relates to sample_seconds and media_path. Baseline 3 is appropriate when structured fields carry parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb 'Find' and resource 'high-motion moments' with clear scope (bounded local video, decoded frame differences). It implicitly distinguishes itself from scene-edit detection by noting that flashes, cuts, and camera movement are not semantically separated, but it does not name a sibling alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use or when-not guidance, and no alternative tools are named. The limitation sentence informs behavior, not selection context, leaving the agent to infer usage from the purpose alone.

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

Deploy Server