Skip to main content
Glama
Sign In
MCP Premiere Pro

MCP Premiere Pro

by Miinwan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

close_all_source_clips

Closes every open source clip in Adobe Premiere Pro to clear the Source Monitor and reset the clip tab area.

Instructions

Premiere Pro expanded operation: close all source clips.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

C2.6/5.0
Behavior1/5

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

No annotations are provided, and the description mentions an 'expanded operation' with no details about destructive effects, output, or side effects. Closing all source clips implies a state-changing operation with no warning.

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

Conciseness3/5

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

One compact sentence and acceptable length, but it leaves out key behavioral specifics (e.g., whether this is a destructive close, whether it closes monitors).

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

Completeness1/5

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

No output schema, no annotations, no sibling comparison, and no context about the larger editing workflow. The description alone is too thin for an AI to safely select this among many media-editing operations.

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, so no parameter help is required; the schema includes no meaningful descriptive properties.

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?

The description names a specific action and target ('close all source clips') with a verb and object, but it does not distinguish this from sibling tools that also close or remove clips.

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 guidance about when to close source clips vs. using alternatives, expected contexts, or fallback behavior; relies on the tool name.

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