Permanently remove a Facebook Page post by its post ID to delete unwanted content from the Page.
Permanently delete a post from the Facebook Page by its post ID.
| Name | Required | Description | Default |
|---|---|---|---|
| post_id | Yes | The Facebook post ID to delete (e.g. '123456789012345_987654321098765') |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full burden. It discloses the critical destructive behavior ('Permanently delete'), which is valuable, but does not cover permissions required, rate limits, or what happens to related data (e.g., comments). This is a gap for a mutation tool.
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 a single, front-loaded sentence that efficiently communicates the tool's purpose without any wasted words. It is appropriately sized for a simple, single-parameter deletion operation.
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 deletion tool with no annotations and no output schema, the description is minimal but adequate on core function. It omits important behavioral details like required permissions, irreversible side effects beyond deletion, and potential error conditions, leaving contextual gaps.
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%, with the lone parameter fully documented in the schema including an example format. The description adds no additional meaning beyond what the schema provides, so the baseline score of 3 is appropriate.
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), resource (a post), scope (from the Facebook Page), and identifier (post ID). It clearly distinguishes itself from sibling tools like facebook_create_post and facebook_get_posts.
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 only through the word 'Permanently' but provides no explicit guidance on when to use this delete tool versus other operations. It lacks context on prerequisites, permissions, or conditions, leaving usage to be inferred.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.