Skip to main content
Glama

link_selection

Link selected items in a Premiere Pro timeline to move or edit them as a single group.

Instructions

Premiere Pro expanded operation: link 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?

With no annotations at all, the description carries the full burden of behavioral disclosure. It reveals nothing about side effects, whether this mutates clip linkage, whether selection is required, or what happens after invocation. 'Expanded operation' is a boilerplate phrase and conveys no actual behavior.

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 under-specified. It spends its only real estate on the empty phrase 'Premiere Pro expanded operation' instead of explaining what linking a selection does, so it is not meaningfully concise.

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?

Despite having no parameters, the tool's semantics are essentially undefined: 'link selection' could mean linking selected clips, linking audio/video, or something else entirely. With no output schema, no annotations, and no behavioral detail, an agent cannot accurately determine what this tool accomplishes or when to invoke it.

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?

There are zero documented parameters and schema description coverage is 100%, so the baseline is 4. The description adds no parameter details, but no parameters exist for it to explain.

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: link selection' merely restates the tool name with a generic 'expanded operation' prefix. It does not specify what 'link selection' means, what gets linked, or how it differs from sibling tools like unlink_selection or link_audio_video.

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 provided. The description gives no indication of when to prefer this tool over alternatives such as link_audio_video or unlink_selection, and no exclusions or prerequisites are mentioned.

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