Tools
list_matches
Lists the events that entered your Views, newest first, with whether an alert email carried each; or one Match in full.
When to use it
- You want which events entered your Views, or one View, and when. With
view_id, read thesummaryfor how the View is doing. - You want which alert emails went out, or which Matches were dropped and why: filter on
delivery_status. - You want one Match in full, with the event's numbers as they were when it matched: pass
match_id. - It replaces
get_match, whose name still answers: see Old names.
Inputs
page(integer): The page of results.limit(integer): Matches per page. A number above 100 reads as 100.view_id(uuid): Only this View's Matches, fromlist_views. It also adds asummaryof the View's window.event_id(string): Only this event's Matches, asevplus ten characters, fromsearch_eventsorscreen_events.since(date-time): Only Matches at or after this time. Leave it out for the last 7 days.delivery_status(string): Only Matches in this state:sentfor the ones an alert email carried,not_sentfor the ones dropped,pendingfor the ones not handled yet,not_applicablefor the ones that could never email.not_applicableselects only Matches recorded when a View learned what it held, not the Matches of a View that sends only to destinations. One ofsent,not_sent,pending,not_applicable.include_snapshot(boolean): Put the full snapshot of the event's numbers, as they were when it matched, on every row. It is large, so a page can be cut to fit; for one Match, passmatch_idinstead.sort(string):matched_at, the one order Matches come in. One ofmatched_at.order(string):desc(the default) for the newest Match first,ascfor the oldest first. One ofasc,desc.match_id(uuid): One Match, as thematch_ida page returns. With it, the answer is that Match in full, and no other input applies.
Examples
Which events entered my Zach Bryan View this week?
{ "view_id": "7c9e6679-7425-40de-944b-e07fc1f90ae7" }Which alert emails actually went out since October 1?
{
"since": "2026-10-01T00:00:00Z",
"delivery_status": "sent",
"limit": 50
}Why did this event enter my View? Show me its numbers when it matched.
{ "match_id": "c4d5e6f7-1a2b-4c3d-8e9f-0a1b2c3d4e5f" }What comes back
- One short row per Match:
match_id,event_id,event_name,local_date,event_url,view_id,view_name,view_url,matched_at, andsignals, a few of the event's numbers that show why it matched. origin:livewhen the event entered on a market change,baselinewhen the Match was recorded as the View learned what it held. AbaselineMatch never sends an alert.delivery_status:sentonly when an alert email carried the Match.not_sentcomes withdelivery_reason, such asmuted_view,locked_view,email_digests_off(alert email is off for the account) orview_disabled.notified_atis set only when the Match wassent; never read delivery from a time.- With
view_id, asummaryfirst: the Matches in the window, the window, the first and last match time, andtop_movers, the five events whose price moved most.scannedsays how many Matches those five came from. - With
match_id: the Match withsnapshot, the event, its numbers and its performer's numbers frozen when it entered the View, and itsdelivery_status. totalandtotalPages. A page too large for one answer comes back as its first rows withmeta.truncated. Columns your plan does not include are left out of the event's numbers.
Limits and quota
- Reads only: it changes nothing.
- Each call spends one MCP request.
- Covers your saved Views and your watched events' Views. On an organization, it also covers the Views shared with the organization.
- The window starts 7 days back unless you set
since.