Skip to main content
Glama

extract_selection

Remove selected clips from the Premiere Pro timeline and close the gap, refining your sequence for a cleaner edit.

Instructions

Premiere Pro expanded operation: extract selection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior1/5

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

No annotations are provided, and the description offers no behavioral disclosure. It does not explain what happens to the selected clips, whether they are deleted, copied, or moved, or any side effects on the timeline.

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?

The description is extremely short, but it is under-specification rather than concise. It offers no useful information beyond a vague restatement of the tool name, and the term 'expanded operation' adds no value.

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?

For a tool with no annotations and no output schema, the description is grossly inadequate. The agent has no idea what 'extract selection' does, what parameters it might accept (even if none), or what the outcome is. This is a complete gap in contextual information.

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 there are no parameter semantics to explain. The baseline of 4 is given for zero-parameter tools, and the description does not need to add parameter meanings.

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 'Premiere Pro expanded operation: extract selection' restates the tool name without any detail on what 'extract selection' does. It does not specify the verb's meaning or resource, and it does not distinguish it from similar siblings like lift_selection, remove_selected_clips, or ripple_delete.

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?

There is no guidance on when to use this tool versus alternatives. It simply names the operation without explaining the use case, prerequisites, or contrast with related tools like lift_selection or remove_selected_clips.

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/compimprove/adobe-premiere-mcp'

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