Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Facebook city events

facebook_events_list
Read-onlyIdempotent

Retrieve public Facebook events for a city from a Facebook Events explore URL, filtered by time window and paginated with a cursor.

Instructions

List Facebook events for a city by explore URL. Requires url. Returns a list (use cursor when paginated).

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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "facebook_events_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Public Facebook Events explore URL for a city.
timeNoOptional time window for events.
cursorNoOpaque pagination cursor returned by a previous response.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered. The description adds only the pagination mechanic ('use cursor when paginated'), which the schema already documents, and says nothing about rate limits, auth, or result ordering/freshness.

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?

Two short sentences, front-loaded with the core action and the required input. The return-value clause ('Returns a list') is mildly redundant given the readOnly list nature, but nothing else is wasted.

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 read-only, single-purpose listing tool with 100% schema coverage and no output schema, the description covers what it does, the required input, and pagination behavior. Only the absence of guidance on result shape or the time-window parameter keeps it from a 5.

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 description coverage is 100%, so every parameter including url, time, and cursor is already documented. The description merely restates that url is required and that cursor handles pagination, adding no meaning beyond the schema; baseline 3 applies.

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 ('List Facebook events for a city') plus the access path ('by explore URL'), which distinguishes it from single-event getters and search tools without naming them. It lacks explicit sibling differentiation, so it stops short of a 5.

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?

'Requires `url`' and 'use cursor when paginated' give operational guidance, but there is no statement of when to choose this over facebook_events_search_list or facebook_profile_events_list, and no exclusions or prerequisites beyond the required param.

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