This page documents the Python MCP surface (
mcp.heybtw.com). It reflects mcp-server/tools/event_summary.py as of this page’s publication — see Schema stability. If your integration expected a tool named get_event_details, this is it — see the naming note below.Naming note. Some earlier internal drafts referred to this capability as
get_event_details. The shipped, registered tool name is get_event_summary — use that name. There is no separate get_event_details tool on this surface.Purpose
get_event_summary is the single-event deep dive: attendance broken into host/partner/external, seniority distribution, per-partner sourcing performance, top engaged accounts, how this event compares to the workspace’s own program average, and (when HubSpot is connected) pipeline attribution for this one event.
When to use this
- “Give me a report on last month’s Robotics Summit.”
- Immediately after an event, to compare it against
program_comparisonand decide whether to repeat the format. - Before
get_invite_recommendationsfor a similar upcoming event, to see who attended last time.
Parameters
Default behavior
Given onlychannel_id, returns the full attendance/funnel/seniority/top-accounts/comparison report without the attendee-level contact list and without the partner performance breakdown — both are opt-in via their respective flags, keeping the default response smaller for the common “just show me the numbers” case.
Sample request
Sample response
Response field reference
Envelope
data[0]
Errors
channel_idrefers to a nonexistent or out-of-workspace channel. The tool raisesValueError(f"Channel {channel_id!r} not found in workspace {workspace_id!r}")internally, but like every tool on this surface, that specific message does not reach the client — it’s caught by the generic handler and surfaces asRuntimeError: Internal error executing get_event_summary (error_id=...). There is currently no way for an agent to distinguish “channel not found” from any other internal failure from the error message alone.channel_idomitted entirely. Same generic error — seeget_workspace_overview— Errors.
Pagination and limits
Not applicable to the report itself — one event in, one report out.contacts (when requested via include_contacts) is capped at 200 with no further pagination; use contacts_raw_total/contacts_total to know if you’re seeing everyone.
Related tools
get_event_attribution— the same event’s pipeline numbers in the multi-event comparison shape, plus sourced/influenced breakdown by company.get_partner_insights— a given partner’s performance across all events, not just this one.get_invite_recommendations— who to invite to a similar future event.