fb_delete_post
Permanently delete a Facebook Page post using its ID. This action cannot be undone.
Instructions
Permanently delete a post from the Facebook Page. This cannot be undone.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| post_id | Yes |
Permanently delete a Facebook Page post using its ID. This action cannot be undone.
Permanently delete a post from the Facebook Page. This cannot be undone.
| Name | Required | Description | Default |
|---|---|---|---|
| post_id | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the behavioral disclosure burden. It explicitly reveals the destructive and irreversible nature of the operation, which is the most important behavioral trait for an AI agent to understand before invoking the 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?
Two concise sentences with the key action and the critical irreversibility warning front-loaded. Every word adds value there is no redundant or unclear content.
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 destructive tool, the description includes the essential context: the action, the target platform/resource, and permanence. It could mention permissions or return behavior, but those are less critical given the simple schema and clear irreversible warning.
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 0%, so the description must compensate, but it adds no detail about what exactly post_id refers to or its expected format. The property name and required marker in the schema carry almost all the meaning.
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?
The description states a specific verb and resource: 'Permanently delete a post from the Facebook Page.' It clearly identifies the tool's function and differentiates it from sibling creation, listing, and retrieval tools.
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 intended use is implied through 'delete a post', and the warning 'cannot be undone' conveys caution. However, it does not explicitly state when to prefer this over alternatives or mention exclusions, even though no sibling provides deletion.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/SwamiSasha/meta-social-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server