Skip to main content
Glama

unlink_selection

Unlink selected clips in Adobe Premiere Pro to break audio-video links or grouped items, enabling independent editing and adjustments.

Instructions

Premiere Pro expanded operation: unlink selection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Install Server

TDQS

C2.3/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, but it only restates the action. It does not explain whether this operation is destructive, requires selected clips, what gets unlinked (e.g., audio/video links), or what side effects occur.

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 wastes the front-loaded 'Premiere Pro expanded operation' phrase, which adds no meaning. The remaining 'unlink selection' is just the tool name rephrased, so the sentence does not earn its place through substantive content.

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 there are no annotations, no output schema, and no parameters, the description is the sole source of guidance, yet it remains ambiguous about what selection is being unlinked and what the operation accomplishes. An agent cannot confidently distinguish this from related operations like link_selection or lift_selection based on the current text.

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 score is 4. The description adds no parameter-specific information, but none is needed; there are no inputs an agent must understand.

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 is essentially a restatement of the tool name: 'Premiere Pro expanded operation: unlink selection.' It provides a verb and resource but adds no definition of what 'unlink' means or what kind of selection is affected, making it barely more informative than a tautology.

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 about when to use this tool versus alternatives like link_selection, lift_selection, or extract_selection. The description offers no context, prerequisites, or exclusions, leaving the agent to infer usage from the name alone.

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