set_start_time
Set the start time for clips or sequences in Adobe Premiere Pro to control playback position and align edits.
Instructions
Premiere Pro expanded operation: set start time.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Set the start time for clips or sequences in Adobe Premiere Pro to control playback position and align edits.
Premiere Pro expanded operation: set start time.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It fails to explain what 'set start time' means operationally, whether it mutates project state, requires certain selections, or has side effects. The description adds no behavioral context beyond the tool's name.
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 a single sentence, but it is mostly boilerplate ('Premiere Pro expanded operation') and restates the tool's name. It is under-specified rather than concise, failing to provide valuable content.
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?
This tool is part of a large API with many sibling operations, but the description gives no context about the object or domain of the start time. There is no output schema or annotations to compensate, making the description critically incomplete for correct use.
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 parameters, so according to the rubric, the baseline is 4. The description adds no parameter details, but the absence of parameters means little is needed. The schema is generic, yet the description does not confuse the matter.
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 start time' provides a verb and a resource ('start time'), but the resource is undefined. It could refer to a clip, sequence, timeline, or effect, and there is no differentiation from sibling tools like set_clip_start_time, making the purpose unclear.
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 given on when to use this tool versus alternatives. There is no mention of limits, prerequisites, or context, leaving the agent without direction on selecting this tool over related ones.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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