delete_pagePermanently delete one of your pages by slug. The link stops working immediately and the slug is freed. Deleting an already-deleted page is a safe no-op.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| ok | Yes | ||
| slug | Yes | ||
| alreadyDeleted | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "alreadyDeleted": {
+ "type": "boolean"
+ },
+ "ok": {
+ "type": "boolean"
+ },
+ "slug": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "ok",
+ "slug"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds rich behavioral details beyond the annotations: permanence, immediate effect, slug being freed, and safe no-op for already-deleted pages. These specifics are not covered by readOnlyHint=false or destructiveHint=true, significantly enhancing transparency.
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 three concise sentences, front-loaded with the core action. Each sentence provides useful information: what it does, immediate effects, and idempotency, with no wasted words.
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 one-parameter delete tool, the description covers the purpose, parameter semantics, behavioral outcomes, and safety (no-op). Annotations cover destructive nature, and an output schema exists, making this complete.
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?
With schema description coverage at 0%, the description compensates by explaining that the 'slug' parameter is the page identifier used for deletion. It doesn't repeat schema constraints but adds semantic meaning that the schema alone doesn't convey.
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 deletes a page permanently by slug, which is a specific verb and resource. It also distinguishes from sibling tools like get_page, list_my_pages, publish, and update_page by focusing on deletion.
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 implies usage for deleting pages but does not explicitly state when to use it versus alternatives. It provides behavioral context about effects (immediate link stop, slug freed, no-op) but lacks explicit when-to-use or when-not-to-use guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.