multiple_undo
Undo several previous actions in Premiere Pro at once by specifying the number of steps to revert.
Instructions
Undo multiple steps at once.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| count | No | Number of undo steps (default: 1) |
Undo several previous actions in Premiere Pro at once by specifying the number of steps to revert.
Undo multiple steps at once.
| Name | Required | Description | Default |
|---|---|---|---|
| count | No | Number of undo steps (default: 1) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. The description only says 'undo multiple steps', but does not disclose limits, whether it's destructive, or if the action itself can be undone. The agent is left guessing about behavioral details.
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?
Extremely concise at only 5 words. It front-loads the action and scope, but lacks any structural elements like sections or examples. For a simple tool, this is acceptable but not exemplary.
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 has one optional parameter and no output schema, the description is minimally adequate. However, it doesn't clarify the context (e.g., active sequence) or provide completeness for an agent unfamiliar with the application.
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?
Schema coverage is 100% (one parameter described). The description adds no meaning beyond the schema; it doesn't mention the parameter count or its default value.
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 undoes multiple steps at once, which is the primary action. However, it doesn't explicitly differentiate from the sibling 'undo' tool, though the name implies multiple steps.
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 explicit guidance on when to use this tool versus 'undo'. The description implies it's for undoing several steps, but lacks when-not-to-use or alternative considerations.
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/leancoderkavy/premiere-pro-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server