Skip to main content
Glama
Sign In
Adobe Premiere Pro MCP

Adobe Premiere Pro MCP

by compimprove
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

stop_playback

Stop current video playback in Adobe Premiere Pro. Use this tool to halt preview or timeline playback instantly, returning the playhead to its current position for precise editing control.

Instructions

Premiere Pro expanded operation: stop playback.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "stop_playback"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only says 'stop playback' without detailing any side effects, such as whether it sets the playhead position, releases resources, or has any impact on the currently active sequence. The phrase 'expanded operation' is vague and not explained.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single concise sentence, front-loaded with 'Stop playback'. However, the phrase 'expanded operation' adds no information and could be removed; the description is minimal but not overlong.

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

Completeness2/5

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

Given no annotations, no output schema, and a simple tool, the description is minimal. It completely lacks context about which playback target (timeline, source monitor) is affected, and whether this applies to the active sequence or all playback. Given the sibling tools play_timeline/play_source_monitor, the description should specify the scope.

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?

The tool has zero parameters, and the schema description coverage is 100% (an empty object). The description doesn't need to explain parameters. Baseline 4 is appropriate since 0 params means no semantics to add.

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

Purpose3/5

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

The description states the tool stops playback in Premiere Pro, which is a clear verb+resource. However, it does not distinguish among the related sibling tools play_timeline, play_source_monitor, and stop_playback, nor does it specify which playback target (timeline vs. source monitor) is stopped.

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?

The description provides no guidance on when to use this tool versus alternatives like play_timeline or play_source_monitor. It does not clarify whether it stops all playback or a specific monitor, nor mention any prerequisites (e.g., playback must be active).

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