Skip to main content
Glama
Sign In

Nilyo

by com.nilyo
OverviewDiscussionsAdmin

Facebook / Messenger: List post reactions

facebook_list_post_reactions
Read-onlyIdempotent

List visible post reactions. Facebook may omit reactors despite nonzero counters; never claim exhaustive coverage.

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": "facebook_list_post_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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent, open-world read. The description adds a genuinely non-obvious behavioral warning — Facebook omits reactors despite nonzero counters, and the agent must not claim exhaustive coverage — which is real value beyond the structured fields. It stops short of covering pagination or result shape (no output schema), but the caveat is the high-value disclosure.

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

Conciseness4/5

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

Two sentences, front-loaded with purpose then the important caveat. No waste, though the caveat could optionally be tied to what to do instead (e.g., report only what is returned).

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 list tool with safety annotations and well-documented params, the description is nearly complete. The omission caveat is the key behavioral fact. It does not describe pagination behavior, but the cursor parameter and limit cap (max 10) in the schema cover that adequately.

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 coverage is 75%, so post_id, account_id, and cursor are already documented in the schema. The description adds no parameter meaning; the cursor's no-offset-pagination note lives in the schema, not the description. Baseline 3 is correct.

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 post reactions'. The 'post reactions' qualifier implicitly distinguishes it from facebook_list_comment_reactions and facebook_list_my_reactions among siblings, though it never names the alternative explicitly, so an agent must still infer the boundary.

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?

No when-to-use or when-not guidance, and no mention of the closest siblings (facebook_list_comment_reactions, facebook_list_my_reactions). The agent must infer applicability from the name and scope alone.

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