Read-only.
channel_id another tool takes. Follows the heyBTW MCP rules.
When to use it
- “What events do we have coming up?”
- “Which events did we run last quarter?”
- “Is anything happening today?”
- “What’s the channel_id for the Austin dinner?”
- “How many people signed up for each event?”
Parameters
All optional. No filter means every event; there is no default time window.
There is no
limit. Every read is a page of at most 25,000 characters: the longest run of matched events, in order, that fits. total_matching counts every event the filters matched, and metadata.pagination states limit, returned, has_more and next_cursor. While has_more is true, call again with the same filters and cursor set to next_cursor. The position is an offset, so an event added or archived between pages can repeat or skip a row: de-duplicate on channel_id.
event_date is a UTC instant. Tell the user the event’s own date and time instead: each row carries event_local_date (YYYY-MM-DD), event_local_time (HH:MM, 24-hour) and event_timezone (an IANA name), the same start on the collab’s calendar. When the collab has no time zone recorded, event_timezone is null and the local date and time are UTC. With no start date all three are null.
Response
One row per event in program scope. Archived and demo collabs are excluded, the same setget_event_attribution reads. With no filter, rows come newest first (metadata.ordering: event_date_desc_then_channel_id); with status: upcoming they come soonest first.
The sample below is trimmed from a real
status: "upcoming", date_from: "2026-11-01" call.
event_date is UTC. The SF open house starts at 01:30 UTC on 10 November, which is the evening of 9 November in its own time zone. Read the event day from get_event_details (goal.clock.event_date), not from this timestamp.
Rules the agent must follow
- Report
roster_countas sign-ups, never as attendance. For who came, callget_event_detailsand readattendance.attended. - Read
event_tenseas served. Never work it out fromevent_dateand today’s date. - This is a directory, not a metrics tool. It carries no revenue, pipeline or funnel field. For revenue use
get_event_attribution. - Use
channel_idfrom these rows; do not guess one.
Errors and gaps
Related
get_event_details: one event’s roster, attendance and goal.get_event_attribution: revenue per event.get_workspace_overview: program totals over the same set of events.- Playbooks: The morning after, Invite sprint.