link_selection
Link selected clips or assets in Adobe Premiere Pro to group them for synchronized editing and movement.
Instructions
Premiere Pro expanded operation: link selection.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Link selected clips or assets in Adobe Premiere Pro to group them for synchronized editing and movement.
Premiere Pro expanded operation: link selection.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure, but it only repeats the concept of 'link selection'. It does not mention side effects, what gets linked, whether the operation is reversible, or any required conditions.
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 very short and front-loaded, but 'Premiere Pro expanded operation' is filler that adds little beyond the tool's name and surrounding context. Conciseness is good, but the space is not used to add meaningful information.
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?
For a mutating action tool with no annotations, no output schema, and a potentially ambiguous link operation, the description is insufficient. It does not explain what selection linking does, how it differs from related tools, or what the expected result is.
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 input schema covers everything by being effectively empty. The description does not need to explain parameter semantics, and the baseline for no parameters is appropriate.
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 states the action ('link') and resource ('selection'), so it is not a pure tautology. However, 'expanded operation' is vague and does not clarify what linking a selection entails, nor does it distinguish this from sibling tools like link_audio_video or unlink_selection.
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?
No guidance is given about when to use this tool versus alternatives such as link_audio_video or unlink_selection. The description does not state prerequisites like having a selection or what kinds of items can be linked.
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/compimprove/adobe-premiere-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server