undo
Revert the last edit in Adobe Premiere Pro to correct mistakes and maintain project accuracy.
Instructions
Performs an undo operation in Premiere Pro.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Revert the last edit in Adobe Premiere Pro to correct mistakes and maintain project accuracy.
Performs an undo operation in Premiere Pro.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It only restates the action ('Performs an undo operation') without explaining scope, side effects, whether it is destructive, or how many steps it undoes. This is insufficient for a mutation tool.
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, front-loaded sentence with no filler or redundant information. It is appropriately concise for a zero-parameter tool.
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 zero-parameter tool with no output schema, the description is minimally adequate but lacks behavioral context such as whether undo works one step at a time or what happens when there is nothing to undo. It is complete enough for basic invocation but not fully informative.
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 and an empty input schema, so there is nothing for the description to document. The baseline score of 4 applies because no parameter information is needed.
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 clearly states the tool performs an undo operation in Premiere Pro, using a specific verb and resource. However, it does not explicitly differentiate itself from sibling tools like redo or multiple_undo, so it falls short of a 5.
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?
The description provides no guidance on when to use undo versus redo or multiple_undo, and it mentions no exclusions or alternative recommendations. The usage context is only implied by the tool name and the phrase 'performs an undo operation.'
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/compimprove/adobe-premiere-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server