Retrieve comprehensive event details from Ticketmaster including dates, venues, prices, images, classifications, and seat maps.
MIT
204,980 tools. Last updated 2026-06-15 02:04
"Ticketmaster" matching MCP tools:
- Fetch event classification categories from Ticketmaster, including segments, genres, and sub-genres. Supports pagination and locale selection.MIT
- Search for live events by artist or performer name. Filter results by country, date range, and sort order using Ticketmaster data.MIT
- Retrieve upcoming events at a venue using its Ticketmaster venue ID. Filter by keyword, date range, and paginate results.MIT
- Search for Ticketmaster events, venues, or attractions by keyword, date, location, or category to find specific event details and purchase options.MIT
- Retrieve detailed information for a specific Ticketmaster event using its unique ID.MIT
Matching MCP Servers
- Alicense-qualityCmaintenanceProvides tools for discovering events, venues, and attractions through the Ticketmaster Discovery API.Last updatedMIT
- AlicenseCqualityCmaintenanceEnables discovery and search of Ticketmaster events, venues, and attractions with advanced filtering options including date ranges, location-based search, and event classifications through the Ticketmaster Partner API.Last updated1MIT
- Creates a deep-link for users to complete bookings on autonomad.ai, automatically unlocking a 1-month free Premium trial with their first completed booking.MIT
- Find live events in any city, including concerts, sports, theater, and comedy. Filter by date, category, and keyword to discover shows or games during your trip.MIT
- Search for concerts, sports, theatre, and festivals across 26+ countries. Filter by keyword, city, date, or category to find events.MIT
- Retrieve trending events by country, category, and page. Filter by classification and locale.MIT
- Find events near a location by specifying latitude/longitude coordinates and search radius. Filter by keyword, category, date, and more.MIT
- Retrieve details for a specific Ticketmaster venue using its ID. Obtain name, location, and other venue data.MIT
- Find events, venues, and attractions by keyword, location, or category. Filter results by date, city, and classification to get targeted listings.MIT
- Search for attractions or artists on Ticketmaster using keyword and classification filters to find events and performances.MIT
- Search for venues on Ticketmaster using keyword, country code, or state code. Retrieve venue information for event planning.MIT
- Find events on Ticketmaster by keyword, city, date range, and classification. Retrieve event listings with specified filters.MIT
- "What's the ticker for…" / "find the CIK for…" / "what's the RxCUI for…" / "look up the ID for…" / "what is X's official identifier" — resolve a user-spoken NAME to the canonical/official identifier other tools require as input. Use FIRST whenever you have a name but need an ID. SUPPORTED TYPES: "company" (returns ticker + 10-digit CIK + company_name from SEC EDGAR + pipeworx://edgar/company/{cik} citation URI; accepts ticker, CIK, or company name as input — auto-disambiguated), "drug" (returns RxCUI + ingredient + brand from RxNorm + pipeworx://rxnorm/{rxcui} citation; accepts brand or generic name). Each call cascades through several lookup endpoints internally — using resolve_entity replaces 2-3 manual lookups.Connector
- REQUIRES one of `event` (single-event mode) OR `topic` (cross-event mode) — call with no args fails. Find arbitrage opportunities on Polymarket via monotonicity violations + partition-sum checks. `event` (recommended for a specific market): pass a Polymarket event slug like "fed-decision-may-2026" or "when-will-bitcoin-hit-150k"; walks child markets, checks date-axis / threshold-axis ordering AND computes the partition_check (sum of YES prices across mutually-exclusive legs — should ≈1; deviations >3pp emit a BUY/SELL EVERY LEG signal). `topic` (for cross-event scanning): pass a seed question like "Strait of Hormuz traffic returns to normal" or "Fed rate decision"; searches related events across the platform, flattens markets, runs the comparator on the union. Cross-event mode catches "...by May 31" vs "...by Jun 30" patterns that single-event misses. SEMANTIC ANCHOR: cross-event pairs require ≥0.30 Jaccard similarity on question tokens (prevents Powell-Fed-Pause being paired with Powell-DOJ-probe); skipped_low_similarity surfaces the rejected pair count. PARTITION FILTER: drops will-person-X / will-manager-Y / will-someone-else- placeholder slugs; partitions with >20% placeholder fraction return null arb signal. Response: opportunities[] (gap_pp, suggested_trade, reasoning, monotonicity violation context), and in event mode partition_check{sum_yes_prices, gap_from_1, placeholders_filtered, suggested_trade}. FILL CHECK: when the partition signal fires, arbitrage.fill_check prices it against live CLOB depth (theoretical_edge_pp_at_book vs realizable_edge_pp at 1000 shares/leg, thin_legs[]) — realizable_edge_pp ≤ 0 means the overround exists only at last-trade, not in the book; do not trade it. For custom sizing use polymarket_fill_risk.Connector
- "What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / "news on Tesla recently" / "what's happening with Apple" — change feed for a company in the last N days/weeks/months in ONE parallel call. Fans out to SEC EDGAR (filings since `since`), GDELT→GNews fallback (news mentions in window — GDELT preferred, GNews when rate-limited or 5xx), USPTO (patents granted; PatentsView API sunset May 2025 so this soft-fails until reactivated). `since` accepts ISO date ("2026-04-01") or relative shorthand ("7d", "30d", "3m", "1y"). Returns structured changes[] grouped by source + total_changes count + pipeworx:// citation URIs. Use entity_profile instead when you want the static profile (filings + fundamentals + LEI + patents) regardless of window.Connector
- Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.Connector