Skip to main content
Glama
Sign In
MCP Premiere Pro

MCP Premiere Pro

by Miinwan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

remove_all_effects

Removes all applied effects from a Premiere Pro clip or sequence, clearing effect stacks when you need a clean starting point.

Instructions

Premiere Pro expanded operation: remove all effects.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

D1.5/5.0
Behavior1/5

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

With no annotations, the description must disclose behavioral traits. It merely says 'remove all effects' without indicating scope, reversibility, potential side effects, or whether it applies to audio/visual effects. This is critically under-specified.

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?

While very short, the single sentence is not informative enough to be considered truly concise; it is under-specified. It lacks necessary context, similar to the 'Process' example.

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?

Given there is no input schema, output schema, or annotations, this description is the sole source of information. It fails to provide essential context such as what objects are affected, how effects are removed, or what happens if no selection exists. Completely inadequate for a tool with this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero parameters, so the description doesn't need to explain parameter details. However, since there are no parameters, the description must clarify what the operation targets (e.g., selected clips vs. entire sequence). It does not, leaving ambiguity about what 'all effects' means.

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?

The description states the tool 'remove all effects' but is vague about what it applies to (selected clips, sequence, etc.). It does not differentiate from siblings like 'remove_effect' or 'remove_effect_by_name'. 'Expanded operation' is unhelpful and unclear.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites, typical use cases, or distinctions from similar tools like 'batch_apply_effect' or 'remove_effect'.

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