SiteCheck Shop & Social

Comments on a public Facebook post as a logged-out visitor

social_facebook_comments

Read-only

Comments on a public Facebook post as a logged-out visitor sees them (the 'Most relevant' comments of the first page load, usually about 10): comment id, author, author link, text, time, reaction count, reply count and link, plus the post's text and total reaction / comment / share counts. From facebook.com via a residential proxy. Related tools on this server, for a different need: social_facebook_groups when you need Facebook group snapshot as a logged-out visitor sees it; social_facebook_posts when you need latest public posts of a Facebook Page as a logged-out. Price: $0.01 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": {
      "url": "<url>"
    },
    "name": "social_facebook_comments"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	Link of a public Facebook post (facebook.com/<page>/posts/<id>, /permalink.php?..., /photo?fbid=..., /reel/<id>)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond readOnlyHint/openWorldHint it discloses real behavioral traits: the logged-out perspective, that only the first page of 'Most relevant' comments (~10) is returned, the residential-proxy source, the $0.01 USDC x402 pricing across Base/Solana/Arc, and that failed calls are not charged. The truncation limit and the charging model are exactly the kind of context an agent cannot get from annotations.

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?

Front-loaded with the operation and scope, and every clause (fields returned, source, alternatives, price) carries information. It is a dense, comma-chained sentence with parentheticals, which costs some readability, but nothing is filler.

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 one-parameter read tool with an output schema and readOnly annotations, the definition covers source, scope, limits, alternatives and cost — an agent has what it needs to call it correctly. The field-by-field enumeration of return values partly duplicates the output schema, and error behavior for non-public or deleted posts is left implicit.

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 100% and the single `url` parameter already enumerates the accepted post URL formats, so the schema carries the load. The description only indirectly adds the requirement that the post be public; it does not add format or validation detail beyond the schema.

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?

The description opens with a specific verb and resource ('Comments on a public Facebook post') and pins down the exact vantage point ('as a logged-out visitor sees them'), plus the ordering ('Most relevant') and depth (first page, ~10 comments). This is enough to distinguish it from every sibling without opening a schema.

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

Usage Guidelines4/5

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

It explicitly routes the agent to two alternatives with conditions: social_facebook_groups for group snapshots and social_facebook_posts for a Page's latest posts. What's absent is a when-not statement — e.g., what happens with private/restricted posts or whether pagination beyond page one is possible at all.

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

All SiteCheck Shop & Social tools Inspect

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

Need Help?