Permanently deletes a Ghost page by ID, removing it from the site when the deletion must be final and cannot be undone.
Permanently delete a page by id. This cannot be undone.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It does disclose the single most important trait — that deletion is permanent and irreversible — but says nothing about required permissions, whether related resources are affected, or what the response returns.
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?
Two short sentences, zero filler, with the destructive nature front-loaded after the core action. Nothing could be removed without losing meaning.
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 one-parameter delete tool with no output schema, warnings about irreversibility are the essential content and they are present. However, with no annotations and no sibling guidance, it leaves gaps around permissions and side effects that an agent authorizing a destructive call would benefit from.
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 0%, but there is only one parameter and the description clarifies it takes a page id. That is enough to call the tool, though it adds no format, validation, or accepted-value detail beyond the schema's 'string' type.
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?
States a specific verb (delete) and resource (page) plus the identifier used, so an agent immediately knows what it does. It does not explicitly differentiate itself from the closely named siblings posts_delete or tags_delete, relying on the resource noun to do that work.
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?
There is no guidance on when to use this tool versus alternatives such as pages_update (to modify rather than remove) or pages_browse. The only implicit signal is the word 'Permanently', which hints it is not a soft-delete path, but no alternative is named.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.