Identify the clip under the playhead in Adobe Premiere Pro to inspect or edit the current timeline moment. Use it to query clip details at the exact cursor position.
Premiere Pro expanded operation: get clip at playhead.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.3.0-ibintec.1Does 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. It discloses no side effects, return shape, active-seqeunce dependency, or error behavior, leaving the agent with only the phrase 'get clip at playhead.'
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 short, but the only meaningful content is a restatement of the tool name. The 'Premiere Pro expanded operation:' prefix is filler that does not earn its place, and no additional useful structure or detail is provided.
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?
With no annotations, no output schema, and only a vague one-line description, the tool is not fully specified. An agent cannot tell what the operation returns, which sequence it operates on, or how it behaves when no clip is at the playhead.
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 documented parameters and 100% schema description coverage, so there is little for the description to add. This matches the baseline for a no-parameter tool; no parameter semantics are needed beyond what the schema already conveys.
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 essentially restates the tool name: 'get clip at playhead.' The 'Premiere Pro expanded operation' prefix is boilerplate and adds no semantic clarity. It does not explain what 'clip' means in this context, whether it applies to the active sequence, or how it differs from get_clip_at_position.
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 usage guidance is provided. There is no mention of when to prefer this tool over siblings like get_clip_at_position, get_selected_clips, or get_playhead_position, and no exclusions or prerequisites are stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.