SiteCheck Shop & Social

Events listed on a Facebook Page's Events tab: event id

social_facebook_events

Read-only

Events listed on a Facebook Page's Events tab (logged-out view): event id, name, date text, place, city, cancelled flag, organiser and event link, plus the Page name. From facebook.com via a residential proxy. Related tools on this server, for a different need: social_facebook_page_contact_info when you need contact details from a Facebook Page's About tab: category; social_facebook_photos when you need latest photos on a Facebook Page's Photos tab: photo id. 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_events"
  }
}

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.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and open-web scope are covered structurally. The description adds genuinely useful context beyond that: the logged-out view, residential proxy sourcing, and the x402 payment model with failed calls uncharged. It says nothing about pagination, result caps, or latency, so it adds value but not rich behavioral depth.

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?

Front-loads the resource and returned fields in the first sentence, then compresses three sibling comparisons into one tight sentence and closes with pricing. No sentence is filler given the cost disclosure requirement.

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?

An output schema exists, so return-value explanation is unnecessary, and the single required param is fully documented. Pricing and sourcing are disclosed, leaving only minor gaps (pagination/limits, what an empty Events tab returns) for a tool of this simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Single parameter with 100% schema description coverage; the schema already explains that 'page' accepts a username, numeric id, or Page URL. The description's mention of 'Page's Events tab' reinforces the accepted input shape but adds no format or edge-case detail beyond the schema, which is acceptable at this coverage level.

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+resource ('Events listed on a Facebook Page's Events tab') and enumerates exactly what comes back (event id, name, date text, place, city, cancelled flag, organiser, event link, Page name). This is distinguishable 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?

Explicitly frames the sibling tools as 'for a different need' and names the condition for each (contact info from About tab, latest photos from Photos tab), which effectively routes the agent. It lacks an explicit positive statement like 'use this when you need a Page's upcoming events', so it stops just short of full when/when-not guidance.

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?