Skip to main content
Glama

lift_selection

Removes selected clips from the Premiere Pro timeline and places them on the clipboard, leaving a gap for repositioning.

Instructions

Premiere Pro expanded operation: lift selection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Install Server

TDQS

C2/5.0
Behavior1/5

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

Annotations are absent, so the description carries the full burden of behavioral disclosure, and it fails: it doesn't state that the operation mutates the timeline, removes selected clips, leaves a gap, or requires an active selection. The phrase 'expanded operation' is opaque jargon that adds no behavioral information.

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 short but empty: six words that restate the name and preface it with a meaningless label ('Premiere Pro expanded operation'). This is under-specification, not efficient conciseness — the brevity comes from having said nothing.

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 mutation tool with no annotations and no output schema, the description must explain the operation's effect and prerequisites, and the sibling extract_selection makes differentiation mandatory. None of that is present, so an agent has no way to call this correctly or infer consequences.

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 and the schema fully covers the input contract, so the description has nothing to add here. The baseline 4 for a zero-parameter tool applies.

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: lift selection' restates the tool name verbatim and adds only the vague modifier 'expanded operation.' It never defines what 'lift' means in Premiere terms, so an agent cannot distinguish it from extract_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 Guidelines2/5

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

No usage context is given: there is no statement of when to call this tool, what state must exist first (e.g., an active selection in the timeline), or which alternatives to prefer. With a large sibling set that includes extract_selection, ripple_delete, and remove_selected_clips, the absence of routing guidance is a serious gap.

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

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/tro2789/scout-premiere-mcp'

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