Skip to main content
Glama

select_item

Select any item in the Adobe Premiere Pro timeline to enable targeted editing, marker placement, or export operations.

Instructions

Premiere Pro expanded operation: select item.

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 supplied, the description bears the full burden of behavioral disclosure, but it reveals nothing beyond the name: no side effects, prerequisites, failure modes, or meaning of 'expanded operation'.

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 not informative; 'Premiere Pro expanded operation' is filler that does not earn its place. The essential purpose is not front-loaded beyond a restatement of the name.

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?

For an ambiguous tool among a very large sibling set, with no annotations and no output schema, this description is far too sparse. An agent cannot tell what to select, what it returns, or what state it changes.

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 input schema defines zero parameters, and there are no property descriptions to compensate for. Even though the schema allows additionalProperties, there are no actual documented parameters, so the description is not required to add parameter detail.

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 restates the tool name ('select item') and adds only 'Premiere Pro expanded operation', which is uninformative. It does not specify what kind of item (project item, clip, timeline item), nor does it differentiate from the many sibling selection tools.

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 guidance is given about when to prefer this tool over alternatives like select_clips_by_name, select_all_clips, or other selection tools. There is no mention of required active sequence/project context or conditions for use.

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