Skip to main content
Glama

select_disabled_clips

Selects all disabled clips in your Adobe Premiere Pro project for quick review, re-enabling, or removal.

Instructions

Premiere Pro expanded operation: select disabled clips.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

With no annotations, the description carries the burden of disclosing behavior, but it merely restates the tool name. It does not explain what 'disabled' means, whether the selection is cumulative, or if any prerequisites exist. This is a minimal disclosure with no added context beyond the name.

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 with no fluff or repetition, making it concise. However, it is under-specified, but for a zero-parameter tool, this length is acceptable. It is front-loaded with the key action.

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?

Given the low complexity and no output schema, the description should still clarify selection behavior and the meaning of 'disabled clips.' It lacks these details, leaving ambiguity about whether it replaces or adds to the current selection and what scope it applies to. The 'expanded operation' phrase adds no concrete value.

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 baseline is 4 per the rubric. The empty schema is appropriate, and there is no need for parameter descriptions.

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

Purpose5/5

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

The description states a specific verb and resource: 'select disabled clips.' This clearly distinguishes it from siblings like select_all_clips, select_clips_in_range, and deselect_all_clips, which target different subsets or actions. The mention of 'Premiere Pro expanded operation' adds context without confusion.

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 description does not indicate whether it replaces the current selection, adds to it, or in what context (e.g., timeline vs project panel) it operates. No exclusions or alternative tool references are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hetpatel-11/Adobe_Premiere_Pro_MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server