Skip to main content
Glama
Sign In
MCP Premiere Pro

MCP Premiere Pro

by Miinwan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

batch_apply_effect

Apply an effect across multiple Premiere Pro clips in one batch operation to reduce repetitive manual edits.

Instructions

Premiere Pro expanded operation: batch apply effect.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description bears the full burden of disclosing behavior, but it only states 'batch apply effect' and adds the vague 'expanded operation'. It doesn't explain whether it operates on selected clips, whether it requires an effect name parameter, or what happens to existing effects. No safety or side-effect information is given.

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?

The description is a single sentence and very short, with no wasted words. However, the phrase 'expanded operation' is ambiguous and could be removed. Overall, it's concise but not maximally informative.

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?

The tool has no output schema, no annotations, and an empty input schema. The description must compensate for this lack of structured information, but it only offers a vague label. For a batch operation, more detail is needed about how the effect is specified and which items are affected, making it highly incomplete.

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?

The schema defines zero properties (parameter count 0), so schema coverage is effectively 100%. The description adds no parameter information—it doesn't even mention that an effect must be specified or how targets are chosen. This meets the baseline but offers no extra meaning.

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 says 'batch apply effect', which clearly identifies the action as applying an effect in batch, distinguishing it from the sibling tool 'apply_effect' by the batch aspect. However, it doesn't elaborate on what type of effect or which clips are targeted, making it clear but not fully specific.

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?

There is no guidance on when to use this tool versus alternatives. The phrase 'expanded operation' hints that it extends 'apply_effect' but never states the specific scenario (e.g., applying an effect to multiple clips). No alternatives or exclusions are mentioned.

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