Skip to main content
Glama
Sign In
MCP Premiere Pro

MCP Premiere Pro

by Miinwan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

select_disabled_clips

Select disabled clips in a Premiere Pro sequence to isolate inactive media for review or batch editing.

Instructions

Premiere Pro expanded operation: select disabled 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": "select_disabled_clips"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3/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 of behavioral disclosure. It only states the selection target and does not disclose whether the existing selection is replaced or added to, how 'disabled' clips are determined, or what conditions must be met for the operation to succeed.

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 short and readable in a single sentence. The phrase 'Premiere Pro expanded operation:' is filler that repeats domain context and adds little value, but the overall length is appropriately minimal.

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?

For a selection-mutating operation with no annotations and no output schema, the description is too thin. It fails to explain selection semantics, prerequisites, or what 'disabled' means in context, especially given the large sibling list containing many selection-related tools.

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 the input schema fully covers inputs and the baseline for 0-parameter tools is appropriate. The description adds no parameter-specific detail, but none is needed.

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 uses a specific verb ('select') and a specific resource ('disabled clips'), making the operation's intent clear. However, the prefix 'Premiere Pro expanded operation' is vague and does not clarify what 'expanded' means, and it does not meaningfully differentiate from sibling selection tools beyond the target state.

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 such as select_all_clips, select_clips_in_range, or set_clip_selection. It does not mention whether an active sequence is required or how this selection relates to other selection operations.

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