Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

facebook_event_details

Retrieve public Facebook event details by URL or ID, including name, description, start and end times, place, address, coordinates, hosts, and attendance counts.

Instructions

facebook: Event Details. GET /v1/facebook/event/details. Get a public Facebook event by its URL or id: name, description, start and end time, place, address, coordinates, hosts, attendance and interested counts. going_count is not on the logged-out page and is omitted. Deleted and private events redirect to a login and fail at 0 credits. 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "facebook_event_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoThe ID of the event
urlNoThe URL of the event, e.g. https://www.facebook.com/events/1705359837159507/

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/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 disclosure burden and does so well: it explains that going_count is absent because the logged-out page omits it, that private/deleted events redirect to login and fail, and it lays out the complete credit model including which failure modes are free. The only gap is output shape/orientation — it lists fields but does not say how they are structured or whether nulls appear for missing place data.

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 purpose and returned fields come first, followed by edge-case and cost details in a logical order, with no filler sentences. The billing paragraph is dense and multi-clause, though every clause conveys actionable information about cost outcomes, so the density is justified rather than wasteful.

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?

There is no output schema, so the description must convey the return surface, and it enumerates the returned fields including the deliberate omission of going_count. Combined with permission/access constraints (public only) and the full cost model, an agent has everything needed to call this correctly and interpret success versus failure.

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 the baseline is 3, but the description adds genuine meaning by stating the event can be fetched "by its URL or id", which clarifies that the two optional parameters are interchangeable lookup keys rather than both being required. It does not state precedence when both are supplied, which keeps it out of the top band.

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 pairs a concrete verb ("Get a public Facebook event") with the resource and identity keys, then enumerates the exact fields returned (name, description, times, place, coordinates, hosts, attendance counts), so the agent knows precisely what it will get. It is clearly distinguishable from profile-level siblings such as facebook_profile_events because it targets a single event by URL or id.

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?

The phrase "Get a public Facebook event by its URL or id" gives a clear positive use case, and "Deleted and private events redirect to a login and fail" supplies an explicit when-not boundary that prevents wasted calls on non-public events. It stops short of naming a sibling alternative for cases like listing all events for a profile, so it does not reach the top band.

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