biletix-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| biletix_trendingA | Trending/featured events on biletix.com. section: "browse" ("Etkinliklere Göz Atın", featured events), "starting_soon" ("24 Saat İçinde Başlayacaklar", starting within 24h), or "all" (every featured event on the homepage). limit 1..50. Returns events (title, start/end, date text, venue, city, price from in TRY, category, event URL; group/tour cards flagged is_group). |
| biletix_search_eventsA | Keyword search over biletix.com's currently featured events (the homepage's SSR listings — concerts, theatre, festivals, sport). query: e.g. "Simge", "Dolu Kadehi Ters Tut", "caz"; city: e.g. "istanbul", "ankara", "izmir" (matches the event's city). limit 1..50. Returns matching events (title, start/end, date text, venue, city, price from in TRY, category, event URL). Note: this searches featured listings only, not the full catalogue — the site's own search page renders client-side. |
| biletix_get_eventA | Full detail for one event. event_url: the event's biletix.com URL (as returned by the trending/search tools, e.g. "https://www.biletix.com/etkinlik/5BG07/TURKIYE/tr/music-aura-16-11-2026-istanbul"). Returns name, description, start/end, status, venue (+ city, geo coordinates, venue-page URL), price from in TRY, availability and image. |
| biletix_list_by_categoryA | Featured events in one category, from the homepage's SSR listings. category: the URL-slug prefix, e.g. "music" (concerts). limit 1..50. Returns events in that category plus the list of categories present on the homepage today (when the homepage is music-heavy, other categories may be empty — the site renders non-music categories client-side). |
| biletix_list_venuesA | Venues behind the homepage's featured events: distinct venue names with city and featured-event count. limit 1..50. Use biletix_get_event to get a venue's page URL, then biletix_venue_events for its upcoming events. |
| biletix_venue_eventsA | Upcoming events at one venue. venue_url: the venue's biletix.com page URL (as returned by biletix_get_event's venue_url field, e.g. "https://www.biletix.com/mekan/340BG/TURKIYE/tr/bostanci-gosteri-merkezi-istanbul"). limit 1..50. Returns the venue name + its events (title, start/end, date text, price from in TRY, event URL). |
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 6 tools
trending, search_events, and list_by_category all return featured events, which creates some overlap, but each has a distinct filter axis (featured/starting-soon, keyword+city, category). get_event, list_venues, and venue_events are clearly distinct and the descriptions explicitly explain their boundaries.
All tools share the biletix_ prefix and snake_case, with verb_noun or verb_resource patterns (search_events, get_event, list_venues, list_by_category). Minor deviations: 'biletix_trending' uses a bare adjective and 'venue_events' drops the verb, but overall predictable.
Six tools is a well-scoped set for a read-only event discovery server, with each tool earning its place (featured browsing, search, detail, category, venue lookup, venue events). Nothing feels redundant or padded.
The browsing lifecycle is mostly covered (list → search → detail → venue drill-down), but search only covers featured SSR listings, not the full catalogue, and there are no date-range or artist-specific filters. Agents wanting non-featured events hit a dead end the descriptions acknowledge.