delete_pages
Remove multiple pages from an Appsmith app with a single API call.
Instructions
Delete multiple pages in one tool call.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| page_ids | Yes |
Remove multiple pages from an Appsmith app with a single API call.
Delete multiple pages in one tool call.
| Name | Required | Description | Default |
|---|---|---|---|
| page_ids | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description should detail side effects (e.g., cascading deletion of widgets), prerequisites, or reversibility. Only states 'Delete multiple pages' which is insufficient for a destructive operation.
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?
Single concise sentence with no wasted words. Perfectly efficient.
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?
Missing prerequisites, expected effects, and output information. For a destructive tool with no annotations and no output schema, description should provide much more.
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 description coverage is 0% and description does not explain what page_ids should contain (e.g., format, source like list_pages). Adds no value beyond schema.
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?
Clear verb ('Delete') and resource ('pages') with batch indication ('multiple pages'), but no differentiation from siblings like 'delete_widgets'.
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 tool vs alternatives (e.g., single page deletion tool). Siblings include many delete tools but description does not provide context.
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/t0knight/appsmith-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server