Skip to main content
Glama
Sign In

Nilyo

by com.nilyo
OverviewDiscussionsAdmin

Facebook / Messenger: Delete comment

facebook_delete_comment
Destructive

Delete the selected comment from this post. External action: preserve explicit user approval. Never retry after an uncertain failure; inspect current state first.

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>",
      "comment_id": "<comment_id>"
    },
    "name": "facebook_delete_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYesFull Facebook post.id (<author_id>_<post_id>) from facebook_list_user_posts or facebook_get_post. Not a URL, text or author ID alone.
account_idNoOwned Facebook unipile_account_id from list_connected_accounts. Not a Facebook person or Page ID. Required when several Facebook accounts exist.
comment_idYesNumeric comment.id from facebook_list_post_comments or facebook_list_comment_replies, paired with that post_id. Not comment text or post ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered; the description adds non-obvious policy context — user approval gating and the no-retry/re-inspect rule — that an agent would otherwise get wrong. It stops short of saying whether child replies are also removed or what happens on permission failure.

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?

Two short sentences, action first then the risk policy, with no filler. Every clause carries operational weight.

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 destructive, non-idempotent delete with full schema documentation and no output schema, the description covers the safety-critical behavior an agent needs. The remaining gap — cascade effects on replies and permission requirements — is a reasonable omission but would strengthen it.

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 100% and the field docs already explain post_id format, comment_id pairing, and account_id disambiguation. The description adds nothing about parameters, so the baseline 3 applies.

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

Purpose4/5

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

The first sentence names a specific verb and resource ("Delete the selected comment from this post"), which is unambiguous. It does not, however, differentiate from generic siblings such as social_delete_comment or facebook_delete_post, so an agent must infer the platform-specific choice.

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?

The description gives real operating conditions — explicit user approval required, no retry after uncertain failure, inspect state first — which shape when/how to call it. It offers no guidance on choosing this over social_delete_comment or on prerequisites such as owning the post or having moderation rights.

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

All Nilyo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources