Sets the position of a clip in Adobe Premiere Pro, allowing precise placement within a sequence timeline.
Premiere Pro expanded operation: set clip position.
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "set_clip_position"
}
}| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It does not disclose any behavioral traits such as whether it mutates state, requires a selected clip, or has side effects. The term 'expanded operation' is unhelpful and does not clarify behavior.
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 extremely short but under-specified. It is not concise in a useful way; it omits critical information. The phrase 'expanded operation' is filler and does not earn its place.
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?
Given the tool's complexity (likely a mutation on a clip), the description is completely inadequate. No output schema, no annotations, and no parameter details. The agent cannot infer how to invoke this tool correctly or what it does.
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 input schema has zero parameters and 100% schema description coverage (vacuously). The description adds no parameter semantics because there are no parameters. Baseline for 0 params is 4, but the description does not explain how the tool knows which clip to affect or what 'position' means, so a 3 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 'Premiere Pro expanded operation: set clip position' is vague. It identifies the tool as an expanded operation but does not specify what 'clip position' means (e.g., position in timeline, spatial position, or playhead). It does not distinguish from siblings like set_clip_start_time, move_clip, or set_playhead_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 guidance on when to use this tool versus alternatives. The description does not mention prerequisites, context, or exclusions. It is unclear whether this is for spatial position, timeline position, or something else.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.