Permanently deletes a Ghost CMS post by its ID, removing it from the blog when content must be retired.
Delete a post permanently
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Post ID to delete (required) |
Changes observed during successful MCP inspections.
v1.0.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. 'Permanently' is a genuine behavioral disclosure of irreversibility, which is the most important trait here. However, it omits authorization requirements, error behavior for nonexistent IDs, and whether deletion cascades.
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?
One four-word sentence that front-loads the verb and resource and includes only the one qualifier that matters. No waste.
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, no-output-schema delete tool, the description covers the essential fact (irreversibility). It could be stronger by routing the agent to bulk_delete for multi-post cases, but nothing critical is missing.
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 100% for the single 'id' parameter, so the schema already documents the argument fully. The description adds no format, prefix, or lookup detail beyond what the schema states, which is the baseline 3 case.
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 ('a post'), and the qualifier 'permanently' signals this is not a soft delete. It is clearly separable from ghost_posts_get/list/create/update, though it never explicitly contrasts with the sibling ghost_posts_bulk_delete.
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 ghost_posts_bulk_delete or ghost_posts_unpublish. The agent must infer from names alone that this is the single-post irreversible path.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.