Skip to main content
Glama
facebook-mcp

facebook-mcp

by tannht

fb_delete_post

DestructiveIdempotent

Permanently delete a Facebook Page post or video through the Meta Graph API. Confirm first, since removal is irreversible and the content cannot be restored.

Instructions

Permanently delete a post or video from the Page. Irreversible: confirm first.

:param post_id: Id of the post/video to delete. :param page_access_token: Optional Page token.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "post_id": "<post_id>"
    },
    "name": "fb_delete_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYes
page_access_tokenNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true and openWorldHint=true, and the description adds important context beyond that: the deletion is permanent and confirmation is required first. It does not explain downstream effects such as what happens to associated comments or permission requirements, so it is not fully exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short, front-loaded with the destructive nature of the operation, and free of unnecessary wording. The parameter notes are compact and support the main instruction.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter destructive tool with an output schema and strong annotations, the description covers the essential warning and parameter roles. It could be more complete on authorization requirements and failure behavior, but nothing critical for invoking it is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for the two parameters. It identifies post_id as the post/video to delete and page_access_token as optional, but it adds little detail about token requirements, ID format, or edge cases.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource: "Permanently delete a post or video from the Page." It clearly distinguishes this destructive operation from sibling tools such as fb_get_recent_posts and fb_publish_post.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides a useful precondition, "Irreversible: confirm first," but does not explicitly state when to use this tool versus alternatives or when not to use it. The usage context is implied by the delete operation rather than fully spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.