Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Facebook event

facebook_event_get
Read-onlyIdempotent

Retrieve a Facebook event's details by URL or event ID. Use it to pull public event information for research, scheduling, or aggregation directly within your agent workflow.

Instructions

Get a Facebook event by URL or event id. Optional inputs: eventId and url.

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

Input Schema

NameRequiredDescriptionDefault
urlNoPublic Facebook event URL.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
eventIdNoFacebook event id when you have it instead of a full URL.
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.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that, and it also omits the important behavioral constraint that at least one of url/eventId must actually be supplied, implying both are freely optional.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is front-loaded and effective. The second sentence ('Optional inputs: `eventId` and `url`') duplicates the schema verbatim and earns little space, though the overall length is not excessive.

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?

For a simple single-record lookup with a fully documented schema and rich annotations, the essentials are present. It still leaves out the mutual-dependency rule between url and eventId and any routing hint to the sibling search/list tools, which an agent needs to call this correctly.

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 all five parameters are already documented, including the context and llm_model plumbing. The description merely restates that eventId and url exist as optional inputs, adding no format or precedence guidance (e.g., what happens if both are passed), so the 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?

The description states a specific verb and resource ('Get a Facebook event') plus the two lookup keys (URL or event id), which cleanly separates it from the sibling list/search tools like facebook_events_list and facebook_events_search_list. It is clear without needing sibling names spelled out.

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 only implied: by saying it takes a URL or event id, it hints that you need an identifier already in hand and should look elsewhere to discover one. It never states when to prefer this over facebook_events_search_list or what to do if you only have a name.

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