Skip to main content
Glama
Sign In
MCP Premiere Pro

MCP Premiere Pro

by Miinwan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

capture_frame

Captures a still image of the current frame from a Premiere Pro sequence, useful for reference, thumbnails, or documentation.

Instructions

Premiere Pro expanded operation: capture frame.

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": "capture_frame"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

C2.1/5.0
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure and fails entirely. It states no side effects, prerequisites, state changes, or output characteristics. An agent has no idea whether this writes a file, modifies the timeline, reads from the playhead, or requires an active project.

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

Conciseness2/5

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

The text is short but this is under-specification rather than conciseness. Like the 'Process' calibration example, the terseness is achieved by stripping all informative content rather than editing for clarity.

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?

Despite the surface simplicity (0 params, no output schema), essential context is missing: what happens to the captured frame, whether it requires an active sequence, and what events or state trigger the capture. Even a simple operation deserves one sentence of behavioral context in a toolset this large.

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 0 parameters with 100% schema coverage, so the baseline of 4 applies per the rubric's '0 params = baseline 4' rule. There is no parameter documentation burden, and the description's lack of parameter context is not penalized.

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

Purpose2/5

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

"Premiere Pro expanded operation: capture frame." merely restates the tool name with a generic wrapper; "expanded operation" is meaningless flavor text that adds no semantic clarity. It doesn't define what capturing a frame entails or differentiate from sibling tools like export_frame or freeze_frame.

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. Given the enormous sibling list including conceptually similar tools like export_frame and set_poster_frame, the complete absence of when-to-use or alternative-avoidance context is a significant gap.

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