Eventbrite Events Scraper MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token from console.apify.com/account/integrations. The server lists its tool without a token, but a call needs one. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_eventbrite_eventsA | Search Eventbrite events by location and keyword, or read events by URL. Returns one flat row per event with dates, venue, category, organizer, and ticket price range. Refused pages and missing events are free rows. Costs 0.003 USD per event with its page read, 0.0015 USD per event from search only, 0.007 USD per search Eventbrite answers (with or without events), plus 0.026 USD per run start. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool there is no risk of misselecting between tools, so the agent's choice is trivial. However, the tool bundles two distinct modes (keyword/location search and URL-based page read) under one name, which can make it unclear which behavior will trigger for a given input.
A single, descriptive snake_case verb_noun name (search_eventbrite_events) establishes a clean, predictable convention with no deviations to compare against.
One tool is thin for a scraping domain that naturally splits into search, event detail, and possibly pagination or batch operations. It is workable but feels under-decomposed, especially given the overloaded input modes.
The tool covers both event discovery (search by keyword/location) and retrieval (read by URL) with rich per-event fields, which handles the core read-only scraper lifecycle. There is no pagination or batch control surfaced, but agents can work around it via repeated calls.