Skip to main content
Glama
Sign In
facebook-mcp

facebook-mcp

by IvanBBaev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Delete comments

facebook_delete_comment
DestructiveIdempotent

Permanently delete up to 50 Facebook Page comments with a required dry-run plan and explicit apply, tracking each outcome. Use when moderation requires irreversible removal after preview.

Instructions

PERMANENTLY delete up to 50 comments. This cannot be undone — prefer facebook_hide_comment, which is reversible. Always requires an explicit apply:true together with the plan_id from a dry run; the server default never applies a delete on its own. Each id gets its own outcome and a comment that is already gone counts as done. Deleting the Page's OWN comment needs pages_manage_engagement; deleting a comment left BY a user also needs pages_read_user_content.

Input Schema

NameRequiredDescriptionDefault
applyNoSet true to actually perform the write. Omitted or false ⇒ the server decides from its configured write mode: usually a dry run that returns a plan preview and changes nothing, but a server (or package) configured apply-first performs the write. To be certain nothing happens, read the result: a dry run always reports the plan and says the write was NOT performed.
plan_idNoThe `planId` returned by a preceding dry-run preview of this same tool. Required for irreversible and spend-tier writes; plans expire a few minutes after they are created.
profileNoPage profile key (e.g. "brand-a") or a raw Page ID. Omitted ⇒ the default Page (FB_PAGE_ID).
comment_idsYesComment IDs to act on — 1 to 50 per call. Each id gets its own outcome, so one bad id does not fail the rest. Split larger sweeps into several calls.
confirm_tokenNoOut-of-band operator token (FB_CONFIRM_TOKEN) authorizing this one irreversible or spend-tier apply. Needed only when the MCP client cannot show a confirmation prompt. Ask the human operator for it; it is not stored between calls and is never echoed back.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.8.0
    • addedInput schema / properties / comment_ids / items / pattern
      Added value: +"^(?=.*\\w)[\\w.-]+$"
  2. First observedv0.7.0

TDQS

A4.9/5.0
Behavior5/5

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

Goes well past the annotations: annotations only flag destructiveHint/idempotentHint, while the description states the deletion is permanent and unrecoverable, explains per-id outcome isolation, clarifies that an already-deleted comment counts as success (consistent with idempotentHint), and spells out the two different Page permissions required for own-comment vs user-comment deletions.

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?

Five tight sentences, front-loaded with the irreversible warning before the safer alternative and the apply/plan mechanics. Every sentence carries either a hazard, an alternative, or a permission fact; nothing is filler.

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

Completeness5/5

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

For a destructive, open-world batch write with no output schema, it covers reversibility, the dry-run/apply/plan_id protocol, batch size guidance (split larger sweeps), per-id result semantics, and permission requirements. An agent has everything needed to call this safely.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3; the description still adds the coupling rule that apply:true must be paired with a plan_id from a prior dry run and that the confirmation token exists for irreversible applies. It does not add anything about profile or confirm_token beyond what the schema already says, so it stops short of a 5.

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?

Opens with a specific verb and resource ("PERMANENTLY delete ... comments") plus a hard scope limit of 50, and immediately contrasts itself with facebook_hide_comment. An agent can distinguish this from delete_post or hide_comment without opening any schema.

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

Usage Guidelines5/5

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

Explicitly names the preferred alternative when reversibility matters ("prefer facebook_hide_comment, which is reversible") and states the mandatory precondition ("Always requires an explicit apply:true together with the plan_id from a dry run"). It also warns that the server default will not apply on its own, closing the main misuse path.

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

Deploy Server

Other Tools