get_event_sellers

Shows one event's anonymous sellers: how concentrated they are, how they moved hour by hour, or chosen sellers' prices.

When to use it

You want to know whether a few sellers hold most of an event's tickets: leave view out.
You want to see whether one seller is adding or pulling tickets: view series, which also gives the seller letters.
You know a seller's letter and want its prices and listings, overall and per section: view market.
It replaces get_event_seller_concentration, get_event_seller_series and get_event_seller_market, whose names still answer: see Old names.

view (string): now (the default): one current reading of how concentrated the sellers are. series: the sellers hour by hour. market: the prices and listings of the sellers you name. One of now, series, market.
event_id (string, required): The event, by its Ticker id (ev plus ten characters), as search_events and the other tools return it.
hours (integer): With series, how many of the most recent hours to return. Leave it out for the last 168 hours, one week. From 1 to 720.
sellers (array of strings): With market, the seller letters, as view series gives them, like ["A", "C"]. Up to 8 items.
range (string): With market, how far back the price series reaches. Leave it out for 7 days. One of 3d, 7d, 30d, 90d, all.
section_ids (array of strings): With market, only these sections, by section_id as get_event_sections gives it.

Do a few sellers hold most of the tickets for this show?

{ "event_id": "ev3rp4z4zhq1" }

Did any seller add tickets in the last 48 hours?

{ "event_id": "ev8k2m4q7x1a", "view": "series", "hours": 48 }

Compare Sellers A and C over the last 30 days.

{
  "event_id": "ev8k2m4q7x1a",
  "view": "market",
  "sellers": ["A", "C"],
  "range": "30d"
}

now: sellers_active, top1_share and top3_share of the tickets with a known seller (0 to 1), hhi and its band shape (spread, concentrated or dominated), coverage_pct and as_of. concentration is null when the event has no reading.
series: points, one per hour, oldest first, with distinct_sellers, attributed_tickets, coverage_pct and tickets per lettered seller, and sellers with each letter's peak_tickets. Letters are an arrival order, not a rank, and match the event page.
market: points over the range with the chosen sellers' prices and listings, and sections with their current listings per section.
No seller is named, ranked or identified, and there is no way to ask for one.

Reads only: it changes nothing.
Each call spends one MCP request.
A heavy tool: an account runs two at a time, and a third waits.
The Ultra plan includes it. Other plans get a plan_required error that names the plan, not an empty answer.
Only the larger sellers get a letter, and only a seller that reached 10 live listings can be chosen in market.
series and market are heavy calls; now is not.