Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

facebook_profile_events

Fetch a public Facebook page's upcoming events in Facebook's listed order, eight per page, and use the returned cursor to retrieve subsequent pages.

Instructions

facebook: Profile Events. GET /v1/facebook/profile/events. Get a public Facebook page's upcoming events, 8 per page, in the order Facebook lists them. total_count is the page's upcoming-event count. Pass cursor from a response, with the same url, for the next page. Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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": "facebook_profile_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL of the public Facebook page
cursorNoThe cursor from the previous response, to get the next page of events

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses page size, ordering, the meaning of total_count, the cursor contract, and a detailed cost model (1 credit on success; errors, blocked, timed-out, invalid and cache hits free). It omits any note on rate limits or what a blocked/empty response looks like, keeping it short of a 5.

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 pagination behavior, then cost. Dense but nearly every sentence carries information; the cost sentence is long and slightly repetitive ('costs nothing' vs 'charged only where...'), which keeps it from a 5.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description must convey return shape; it explains total_count and cursor but not the structure of individual event records. For a two-parameter read tool this is adequate but leaves the response payload partly unspecified.

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?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: the cursor must be paired with the same url to page correctly, a constraint not stated in the schema. It also clarifies that url must point at a public page.

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: 'Get a public Facebook page's upcoming events,' plus scope details (8 per page, Facebook's ordering). It is clearly distinct from profile/posts tools, though it never names a sibling such as facebook_event_details for single-event lookups.

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

Usage Guidelines3/5

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

Gives concrete pagination guidance ('Pass cursor from a response, with the same url, for the next page') and cost conditions, which tells the agent how to iterate. It does not say when to prefer this over facebook_event_details or facebook_profile_posts, so alternative selection is left to inference.

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

Deploy Server

Other Tools