TickerDocs
Tools

get_venue_schedule

Shows what is on at one venue, its sale dates and weather; finds venues and ids; or shows what each section costs.

When to use it

  • You have a venue and want its upcoming events, soonest first, with the roof type and the coming week's weather.
  • A question names a building, or a place and a size, and you need venue ids: set view to venues.
  • You want what each section at a venue costs across its next events: set view to sections.
  • To rank a venue's events by price, demand or inventory, use screen_events.

Inputs

  • view (string): schedule (the default): one venue's events. venues: find venues by name, state, country or capacity, with their ids. sections: what each section at one venue costs across its next upcoming events. One of schedule, venues, sections.
  • venue_id (string): With schedule or sections, the venue as a Ticker venue id. Leave it out only when you give venue_name.
  • venue_name (string): The venue's name, or part of it, as its official name: Madison Square Garden, not MSG. With schedule or sections the best match is read, so when two venues share a name, find the id first with view venues. Up to 80 characters.
  • days (integer): With schedule, how many days ahead to look when you give neither date_from nor date_to: 30 when you leave it out, at most 365. A larger number reads as 365.
  • date_from (date-time): With schedule, only events on or after this time, ISO 8601 with Z or an offset. With date_from alone, the window runs one year from it.
  • date_to (date-time): With schedule, only events before this time, ISO 8601 with Z or an offset. With date_to alone, the window starts now.
  • page (integer, default 1): With schedule, the page of the window to read, soonest first, limit events a page. The first page when you leave it out.
  • limit (integer): With schedule, the most events: 200 when you leave it out. With venues, the most venues: 5 when you leave it out, at most 25.
  • state (string): With venues, only venues in this state or province, by its code, like TX. A venue with no state on record matches its country code instead. Up to 120 characters.
  • country (string): With venues, only venues in this country, by its two-letter code, like US. Up to 120 characters.
  • capacity_min (integer): With venues, only venues that hold at least this many people. From 0 to 1000000.
  • capacity_max (integer): With venues, only venues that hold at most this many people. It cannot be less than capacity_min. From 0 to 1000000.
  • events (integer): With sections, how many of the venue's next upcoming events to average over, soonest first: 10 when you leave it out, at most 20.

Examples

What is on at Madison Square Garden in December?

{
  "venue_name": "Madison Square Garden",
  "date_from": "2026-12-01T00:00:00Z",
  "date_to": "2027-01-01T00:00:00Z"
}

What is the venue id for Barclays Center?

{ "view": "venues", "venue_name": "Barclays Center" }

What does each section at Barclays Center cost across its next five events?

{ "view": "sections", "venue_name": "Barclays Center", "events": 5 }

What comes back

  • schedule: venue with venue_id, venue_name, city, state and roof (open, retractable, fixed or null), and events, soonest first, with event_id, event_name, local_date, onsale_date, presale1_date and the get-in price now, before fees and all-in.
  • forecast: the venue's next 7 local days, today first, with the high and low in Fahrenheit, the sky, rain and wind. On a plan without it, it is left out and named in withheld.
  • window, the dates read, and has_more true when the window holds more events than came back: ask for the next page. null when no venue matches venue_name.
  • venues: data, one row per venue with venue_id, name, city, state, country_code and upcoming_events, the best name match first. Pass venue_id back with view schedule, or to screen_events.
  • sections: per section, dearest first, the average get-in and median, before fees and all-in, open tickets and listings, and events, how many events the row stands on. events_read under events_considered means some events' listings could not be read.

Limits and quota

  • Reads only: it changes nothing.
  • Each call spends one MCP request.
  • The Pro plan and above include the forecast. Past events, parking passes and other non-admission items are not listed.
  • With venues, give a name or at least one other filter; only venues with an upcoming event are listed, and a capacity bound leaves out venues whose capacity is not known.
  • It replaces find_venue, whose name still answers: see Old names.

On this page