SiteCheck Shop & Social

Latest public posts of a Facebook Page as a logged-out

social_facebook_posts

Read-only

Latest public posts of a Facebook Page as a logged-out visitor sees them (Facebook shows the first 1-3 posts without login): post id, link, text, time, reaction / comment / share counts and media type, plus the Page name and follower count. From facebook.com via a residential proxy. Related tools on this server, for a different need: social_facebook_comments when you need comments on a public Facebook post as a logged-out visitor; social_facebook_followers_following when you need Facebook Page follower counts from Facebook's public Page. 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": {
      "page": "<page>"
    },
    "name": "social_facebook_posts"
  }
}

Input Schema

Name	Required	Description	Default
`page`	Yes	Facebook Page username (e.g. NASA), numeric id or Page URL

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses the key behavioral constraint (Facebook only shows the first 1-3 posts without login), the retrieval path (facebook.com via residential proxy), and the billing model ($0.01 USDC per successful call via x402; failures not charged). That is materially more than the annotations provide and directly affects whether an agent should call it.

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?

The core capability and its logged-out limitation are front-loaded, and the sibling routing follows logically. The enumerated return fields are somewhat redundant given an output schema exists, and the pricing clause is dense, but no sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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, the definition covers scope, the login-gated result limit, data source, cost, and alternatives. With an output schema present, it needn't explain return structure, so nothing an agent needs before calling is missing.

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 'page' parameter is fully documented with accepted formats (username, numeric id, URL), so the schema already carries the semantics. The description adds no further parameter-level detail, which is acceptable but not additive.

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?

States a specific verb and resource (retrieve latest public posts of a Facebook Page) and enumerates the returned fields, scoping it as the logged-out view. It explicitly differentiates itself from social_facebook_comments and social_facebook_followers_following, so an agent can pick it without opening sibling schemas.

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

Usage Guidelines5/5

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

Usage is routed explicitly: use this for a Page's public posts, use social_facebook_comments for post comments, and social_facebook_followers_following for Page follower data. The phrase 'for a different need' plus the concrete condition for each alternative leaves little to infer.

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?