Skip to main content
Glama

facebook_event_search

Search Facebook events by topic and city — local startDate/timezone, venue. 2 credits. Costs 2 credits. Empty results and failures are never charged. Pass cache=true for a free 24h cache hit (default always fresh).

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": {
      "q": "<q>"
    },
    "name": "facebook_event_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesTopic keyword, e.g. 'comedy'. Pair with location for city-scoped results.
toNoInclusive local start date filter YYYY-MM-DD.
fromNoInclusive local start date filter YYYY-MM-DD. Use for upcoming-only windows — Facebook/SERP may return past events.
cacheNoSet true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh.
limitNoMax items to return (default 20, max 200). Flat 2 credits per call. Response `source` is native or extended (fetch path — not a price change).
fieldsNoOptional comma-separated keys to keep on each result row (or on the object for single-item tools), e.g. id,url,publishedAt,engagement. Pagination keys are always kept. Does not change the price.
compactNoDefault true here: drop signed media URLs (video, image, avatar links and their expiry stamps) to keep the response small. Ids, permalinks, dates, text and metrics stay. On Threads, Facebook, Meta Ad Library and TikTok Shop tools request timings are dropped too. Pass false for the full body.
locationNoCity/place geo filter (e.g. London). Matches timezone, location.city, or coords near the city — not a title substring.
upcomingNoWhen true and from is omitted, sets from to today's UTC date so past events are dropped.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / compact / description
      Previous value: -"Default true here: drop signed media URLs (video, image, avatar links and their expiry stamps) to keep the response small. Ids, permalinks, dates, text and metrics stay. Pass false for the full body."New value: +"Default true here: drop signed media URLs (video, image, avatar links and their expiry stamps) to keep the response small. Ids, permalinks, dates, text and metrics stay. On Threads, Facebook, Meta Ad Library and TikTok Shop tools request timings are dropped too. Pass false for the full body."
  2. Changed2 schema fields changed
    • addedInput schema / properties / compact
      Added value: +{
      +  "default": true,
      +  "description": "Default true here: drop signed media URLs (video, image, avatar links and their expiry stamps) to keep the response small. Ids, permalinks, dates, text and metrics stay. Pass false for the full body.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / fields
      Added value: +{
      +  "description": "Optional comma-separated keys to keep on each result row (or on the object for single-item tools), e.g. id,url,publishedAt,engagement. Pagination keys are always kept. Does not change the price.",
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / cache / description
      Previous value: -"Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh. Envelope includes cached + cachedAt on hits."New value: +"Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh."
  4. Changed4 schema fields changed
    • changedInput schema / properties / cache / description
      Previous value: -"Set true to serve from the 24h response cache. Default false — always fetch fresh data."New value: +"Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh. Envelope includes cached + cachedAt on hits."
    • changedInput schema / properties / from / description
      Previous value: -"Inclusive local start date filter YYYY-MM-DD."New value: +"Inclusive local start date filter YYYY-MM-DD. Use for upcoming-only windows — Facebook/SERP may return past events."
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return (default 20, max 200). Billed 2 credits flat on the native path; ~2 credits per returned event on the Apify fallback — check `source` in the response."New value: +"Max items to return (default 20, max 200). Flat 2 credits per call. Response `source` is native or extended (fetch path — not a price change)."
    • changedInput schema / properties / upcoming / description
      Previous value: -"When true and from is omitted, sets from to today's UTC date."New value: +"When true and from is omitted, sets from to today's UTC date so past events are dropped."
  5. Changed6 schema fields changed
    • addedInput schema / properties / from
      Added value: +{
      +  "description": "Inclusive local start date filter YYYY-MM-DD.",
      +  "type": "string"
      +}
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return. Default 20, max 200. Billed per result."New value: +"Max items to return (default 20, max 200). Billed 2 credits flat on the native path; ~2 credits per returned event on the Apify fallback — check `source` in the response."
    • addedInput schema / properties / location
      Added value: +{
      +  "description": "City/place geo filter (e.g. London). Matches timezone, location.city, or coords near the city — not a title substring.",
      +  "type": "string"
      +}
    • changedInput schema / properties / q / description
      Previous value: -"Topic and/or place, e.g. 'comedy Chicago' (min 2 chars)."New value: +"Topic keyword, e.g. 'comedy'. Pair with location for city-scoped results."
    • addedInput schema / properties / to
      Added value: +{
      +  "description": "Inclusive local start date filter YYYY-MM-DD.",
      +  "type": "string"
      +}
    • addedInput schema / properties / upcoming
      Added value: +{
      +  "description": "When true and from is omitted, sets from to today's UTC date.",
      +  "type": "boolean"
      +}
  6. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return. Default 20, max 200. Flat 2 credits on native success."New value: +"Max items to return. Default 20, max 200. Billed per result."
  7. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return. Default 20, max 200. Billed per result."New value: +"Max items to return. Default 20, max 200. Flat 2 credits on native success."
  8. Changed1 schema field changed
    • changedInput schema / properties / cache / description
      Previous value: -"Responses are cached for 24 hours by default. Set false to bypass the cache and always fetch fresh data (default true)."New value: +"Set true to serve from the 24h response cache. Default false — always fetch fresh data."
  9. Changed1 schema field changed
    • addedInput schema / properties / cache
      Added value: +{
      +  "description": "Responses are cached for 24 hours by default. Set false to bypass the cache and always fetch fresh data (default true).",
      +  "type": "boolean"
      +}
  10. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations present, the description carries the full disclosure burden, and it handles the most consequential trait well: costs 2 credits per call, and empty results or failures are never charged. Caching behavior (default always-fresh, opt-in free cache hit) is also disclosed. It stops short of return-shape, result ordering, or auth/rate-limit context.

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 purpose and then the cost/caching facts, which is the right order for a priced tool. However, '2 credits. Costs 2 credits.' is an outright duplicate sentence that does not earn its place.

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 9-parameter tool with no output schema and no annotations, the description plus the very rich schema covers billing, caching, date filtering, and result shaping adequately. The main residual gap is what a result row looks like and how the 'native vs extended' source affects output, which is only hinted at in the schema.

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%, and the schema already spells out q, from/to inclusivity, cache credits, limit caps, and compact defaults in detail. The description only echoes the q/location pairing and cache flag, adding little semantic meaning the schema does not already provide, 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?

States a specific verb and resource ('Search Facebook events') plus the scoping facets (topic, city, local startDate/timezone, venue), so an agent knows exactly what the tool returns. It does not differentiate itself from nearby siblings such as facebook_event_details or facebook_profile_events, leaving that disambiguation to the agent.

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?

The description gives implicit context — topic keyword plus city for scoped results — and one concrete usage instruction ('Pass cache=true for a free 24h cache hit'). There is no explicit when-not-to-use guidance and no mention of an alternative tool for event details or profile-scoped events.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.