Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Facebook profile events

facebook_profile_events_list
Read-onlyIdempotent

Lists events hosted by a public Facebook profile or Page using its URL, with cursor-based pagination to retrieve additional results.

Instructions

List events hosted by a Facebook profile or Page. 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_profile_events_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Public Facebook profile or page URL.
cursorNoOpaque pagination cursor from 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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuine value by disclosing that results are a list and that pagination uses the cursor, but it says nothing about private/blocked profiles, result caps, or failure modes for an open-world scraper.

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?

Three short, front-loaded sentences with no filler; the scope comes first and the pagination note last. 'Requires `url`' slightly duplicates the schema's 'Required. Public Facebook profile or page URL.' but it is a minor redundancy.

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?

There is no output schema, yet the description only says 'Returns a list' without indicating what an event record contains or how many results to expect. For an open-world scraping tool with a required analytics/model parameter, that leaves the agent with a partial picture of the response.

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%, so every parameter including url and cursor is already documented in the schema. The description only reiterates the url requirement and mentions cursor for pagination, adding little beyond the structured fields — the expected baseline of 3.

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 events hosted by a Facebook profile or Page') and scopes it to profile/Page-hosted events, which meaningfully narrows it against the broader facebook_events_list sibling. It does not explicitly name an alternative, so it falls 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?

Usage is implied by the scope phrase 'hosted by a Facebook profile or Page' and the prerequisite 'Requires url', which tells the agent what input is needed. There is no explicit when-to-use/when-not-to-use guidance or named alternative (e.g. facebook_events_list vs facebook_profile_events_list), leaving selection 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