delete_page_layout_snapshot
Remove a saved layout snapshot from a specific page to update or clean up design versions.
Instructions
Delete the layout snapshot for a page
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| pageIndex | Yes | Page index |
Remove a saved layout snapshot from a specific page to update or clean up design versions.
Delete the layout snapshot for a page
| Name | Required | Description | Default |
|---|---|---|---|
| pageIndex | Yes | Page index |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must carry full burden. It only states 'Delete', omitting details like irreversibility, error handling (e.g., if no snapshot exists), or permission requirements.
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?
A single, concise sentence. No unnecessary words, but could benefit from additional context without becoming verbose.
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 simple delete operation, the description provides the core purpose. However, lacking behavioral context like reversibility and error states reduces completeness given the absence of annotations.
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% with parameter 'pageIndex' described as 'Page index'. The description adds no extra meaning, so baseline score of 3 applies.
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 action (delete) and the resource (layout snapshot for a page). It distinguishes from the sibling 'delete_all_page_layout_snapshots' which deletes all snapshots.
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 versus alternatives. Does not mention that this deletes a single snapshot while 'delete_all_page_layout_snapshots' deletes all. No context on prerequisites or use cases.
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/zachshallbetter/indesign-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server