Skip to main content
Glama

select_item

Selects a specified item in Adobe Premiere Pro's project or timeline, enabling AI agents to target and manipulate specific media assets during video editing automation.

Instructions

Premiere Pro expanded operation: select item.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it reveals nothing about side effects, selection semantics, or dependencies. The phrase 'select item' adds no transparency beyond the name.

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 under-specified rather than concisely informative. It is a fragment that does not form a complete sentence and provides minimal useful content, failing the purpose of a description.

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?

Given no annotations, no output schema, and an extremely vague description, this tool is critically underdocumented. The presence of many selection-related sibling tools makes a clear explanation of selection behavior essential, and its absence is a significant gap.

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 0 parameters, and the schema coverage is effectively 100% because none exist. The description adds no parameter meaning, but with no parameters to document, the baseline of 4 is appropriate. However, it could have clarified what the selection operates on, which it does not.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Premiere Pro expanded operation: select item.' merely restates the tool name without specifying what kind of item, in what context, or how selection works. It is a tautology that does not distinguish from sibling selection tools like select_all_clips or set_clip_selection.

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?

The description gives no guidance on when to use this tool versus alternatives. It lacks any context about selection scenarios, prerequisites, or exclusions, so an agent has no basis for choosing it over related tools.

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

Install Server

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/hetpatel-11/Adobe_Premiere_Pro_MCP'

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