Set the start time for a clip or sequence in Adobe Premiere Pro to control timing and align edits precisely.
Premiere Pro expanded operation: set start time.
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_start_time"
}
}| 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, and the description only restates the operation. It does not disclose side effects, whether existing time values are overwritten, what object must be selected, undo behavior, or what 'expanded operation' means.
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 and front-loaded, but 'expanded operation' is vague filler. It is concise rather than helpful, lacking the necessary scoping to earn full credit.
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 mutation tool with no annotations, no output schema, and many similarly named sibling tools, this one-sentence description is severely under-specified. It does not identify the target object, required input, or resulting behavior, making correct invocation very unlikely.
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 defines no named properties but allows arbitrary properties via additionalProperties; the description does not explain how to pass the start time value, what property key to use, or whether time is in seconds, frames, or timecode. The agent is left guessing despite the tool being a setter.
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 restates the tool name ('set start time') without identifying what entity's start time is being set (clip, sequence, playhead, etc.). 'Premiere Pro expanded operation' adds no semantic differentiation and does not distinguish this from siblings like set_clip_start_time 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 is provided on when to use this tool versus alternatives such as set_clip_start_time or set_sequence_in_out_points. There are no usage contexts, prerequisites, or exclusions mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.