get_event_bundle

Reads one event's analytics, price series and sections in one call, as a short summary or as each part's rows.

When to use it

You want more than one of an event's analytics, price series and sections, and one call instead of three.
You want a quick read of an event: where its price started, bottomed and peaked, and which sections are cheapest now.
You want one part in full, with every input it takes: use get_event_analytics, get_event_chart or get_event_sections.

event_id (string, required): The event, by its Ticker id (ev plus ten characters), as search_events and the other tools return it.
parts (array of strings): Which parts to read: analytics, chart, sections. Leave it out for all three. One of analytics, chart, sections.
range (string, default 28d): How far back the price series reaches: 28 days when you leave it out. all reaches back up to one year. One of 7d, 14d, 28d, 90d, all.
rows (boolean, default false): Leave it out, or false, for the summary. true gives each part's rows: the full analytics row, each date of the series, and each section's prices with its last 7 days.

Give me a quick read on this show: prices, where the price has been this month, and the cheapest sections.

{ "event_id": "ev3rp4z4zhq1" }

Show me this game's price path over 90 days and its sections, with every row.

{
  "event_id": "ev8k2m4q7x1a",
  "parts": ["chart", "sections"],
  "range": "90d",
  "rows": true
}

By default, a summary of each part: the headline analytics (prices, listings and demand now), the series' first and last day, its day with the lowest all-in price and its day with the highest median, and the top 10 sections now.
With rows true, each part's rows. A part too long for one answer is cut to fit and carries a pointer to the tool that reads it in full.
A part that fails answers error with the reason, and the other parts still answer.
event_id, event_url and event_name name the event.

Reads only: it changes nothing.
Each call spends one MCP request.
The parts are read together, so that one request covers all three.
Each part follows the plan gates of the tool that reads it in full: a source or column your plan does not include is left out or named in withheld, as there.
The Max plan and above include events that have already taken place.