Skip to main content
Glama

captapi

by io.github.CDCStream

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).

Input Schema

TableJSON 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).
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.

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and delivers meaningful behavioral disclosures: '2 credits', 'Empty results and failures are never charged', and 'Pass cache=true for a free 24h cache hit (default always fresh)'. This is valuable economic and caching context. It does not cover rate limits, latency, or fetch-path behavior, but the disclosed traits are substantive.

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 description is compact and front-loads purpose before cost and cache details, which is good structure. However, '2 credits. Costs 2 credits.' is a direct duplication of the same information — a sentence that fails to earn its place and indicates sloppy editing.

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 moderate-complexity tool (7 params, all schema-documented), the description plus schema cover purpose, result content, cost, cache, and failure-charge policy reasonably well. Gaps remain: no explicit sibling routing, no output schema to describe return shape beyond a partial hint, and no operational limits like rate ceilings. Adequate but not complete.

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 the baseline is 3 and the schema already documents all seven parameters. The description adds only marginal reinforcement — it restates cache behavior ('Pass cache=true for a free 24h cache hit') and references 'local startDate/timezone' which maps to the to/from filters, but adds no new format or syntax details beyond the schema.

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 states a specific verb and resource — 'Search Facebook events' — with a clear scope: 'by topic and city'. It further specifies result content ('local startDate/timezone, venue'), which lets an agent distinguish this from facebook_event_details (single-event retrieval) and facebook_profile_events (profile-scoped events) without opening either schema.

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 context is implied by the scope phrase 'Search Facebook events by topic and city' — an agent can infer this is the tool for topic/city-based event discovery. However, there are no explicit alternatives, exclusions, or when-not-to-use conditions, and several closely related siblings (facebook_event_details, facebook_profile_events) are not mentioned.

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

All captapi toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0
Disambiguation3/5

The platform-prefix convention keeps most of the 178 tools clearly separated, but several clusters are genuinely ambiguous: tiktok_live_info is explicitly described as 'Identical to TikTok Live', instagram_basic_profile and instagram_channel_details both return profile stats, and facebook_profile_posts overlaps with facebook_profile_reels. The generic 'Summarizer' descriptions for facebook_summarize, instagram_summarize, and tiktok_summarize provide no disambiguating detail at all.

Naming Consistency4/5

The dominant snake_case platform_resource_suffix pattern is followed remarkably consistently across 178 tools (e.g. youtube_channel_videos, tiktok_search_users, reddit_subreddit_posts). Minor deviations exist: the same creator resource is called 'channel' in some tools (tiktok_channel_details, instagram_channel_posts) but 'profile' or 'user' in others (facebook_profile_posts, twitch_user_videos, linnkme_profile); link-in-bio tools mostly use _page but linkme uses _profile; and the video_summarize/video_transcript pair lacks a platform prefix.

Tool Count2/5

At 178 tools this is far beyond what any agent can efficiently navigate in a single flat namespace, and even individual platform subsets exceed reasonable bounds (TikTok alone has ~34 tools, YouTube ~25). The sheer breadth of the multi-platform scope partially justifies the count, but the server would be far more usable split into per-platform servers.

Completeness4/5

The read-only data surface is impressively thorough: nearly every platform has profile + content + search + comments coverage, and TikTok, YouTube, Instagram, and Facebook are covered end-to-end including shops, ads, transcripts, and summaries. Notable gaps are minor: Twitter has no keyword search tool, LinkedIn lacks comments, and Reddit has no user-profile endpoint, but none of these create dead ends for the server's core data-retrieval purpose.

Resources