Skip to main content
Glama
Sign In

Nilyo

by com.nilyo
OverviewDiscussionsAdmin

Facebook / Messenger: List comment reactions

facebook_list_comment_reactions
Read-onlyIdempotent

List visible reactions on the selected comment; counters do not prove list completeness.

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_list_comment_reactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNoOpaque next_cursor from the previous page of this same account, identity and resource. No offset pagination.
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.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds a genuinely non-obvious behavioral caveat — that reaction counters do not prove list completeness and only "visible" reactions are returned — which tells the agent to distrust totals and paginate.

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?

One sentence, front-loaded with the action and resource, with the completeness caveat appended. Nothing is redundant or padded.

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 read-only paginated list tool with no output schema, the description plus the cursor and ID semantics in the schema cover what an agent needs. The only omission is any mention of pagination flow or the response shape, which the description leaves entirely to the schema.

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 80%, with post_id, comment_id, cursor and account_id all documented, so the schema carries the parameter burden. The description adds no format or pairing detail beyond what the schema already states about comment_id and post_id.

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?

States a specific verb and resource ("List visible reactions on the selected comment"), making the scope narrower than a post-level or account-level reaction listing. It doesn't explicitly name the near-siblings (facebook_list_post_reactions, facebook_list_my_reactions) to route the agent, but the comment-scoped phrasing is clear enough on its own.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus facebook_list_post_reactions or facebook_list_my_reactions, nor any prerequisite note beyond the implicit need for a comment_id. The only guidance is a caveat about counters, not about tool selection.

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