lift_selection
Lifts the selected clip out of the timeline and closes the gap, leaving other clips unaffected.
Instructions
Premiere Pro expanded operation: lift selection.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Lifts the selected clip out of the timeline and closes the gap, leaving other clips unaffected.
Premiere Pro expanded operation: lift selection.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must fully disclose behavior, but it only says 'lift selection'. It does not explain whether the operation is destructive, whether it leaves a gap, how it interacts with tracks or selections, or any side effects. This is a serious transparency gap for a timeline-modifying tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is one line but offers no substantive content. This is under-specification rather than conciseness; every word should earn its place, but 'Premiere Pro expanded operation' is filler and 'lift selection' only restates the name.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool operates as part of a large set of timeline editing tools, yet the description provides no context on what the operation does, when it is useful, or what effects it has. There are no annotations or output schema to compensate, making the description wholly inadequate for an agent to understand and invoke the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the schema is empty and the description cannot add parameter-level meaning. Per the rubric, 0 parameters gives a baseline of 4. The description does not need to explain parameters that do not exist.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Premiere Pro expanded operation: lift selection' essentially restates the tool name and adds a vague 'expanded operation' qualifier. It does not define what 'lift' means (e.g., removing selected clips while leaving a gap) nor distinguish it from sibling 'extract_selection' which likely removes and closes gaps.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 like extract_selection, ripple_delete, or remove_selected_clips. No prerequisites or context (e.g., must have an active selection) are mentioned, leaving the agent without decision criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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