save_event_context

Writes to your heyBTW workspace: it appends one context entry to one of your own collabs. It changes nothing else, sends nothing, and never writes to the event platform.

Reach for it when you and the user have worked out why an event exists, who it is for, or how to frame the invite. Save it on the collab instead of leaving it in this conversation. Follows the heyBTW MCP rules.

When to use it

“Save that brief so we have it next week.”
“Keep both invite drafts, the VIP one and the general one.”
“Note why we picked these accounts for the dinner.”
“Update the VIP invite with the new subject line.”

Parameters

Parameter	Type	Required	Notes
`channel_id`	string	Yes	The collab, from list_events.
`kind`	string	Yes	`brief`, `audience_rationale`, `invite_draft` or `note`.
`body`	string	Yes	The text, at most 20,000 characters. Line breaks are kept.
`client_request_id`	string	Yes	A fresh hyphenated UUID for this save.
`title`	string	No	Names the entry within its kind, at most 120 characters (“VIP invite” and “General invite” are two invite drafts). May be omitted for a single brief.
`supersedes_entry_id`	string	No	To revise: the old entry’s id, with the same kind and title.
`contract_version`	string	No	Omit for v1, the only version advertised.

Workflow

There is no preview step. One call saves one entry.

Agree the text with the user

Save what you worked out together.

Save with a fresh client_request_id

On a transport error, retry with the SAME id: a committed save is replayed (idempotent_replay: true), never repeated. Reusing the id for a different entry is refused.

Revise by superseding

Entries are append-only and never overwritten. To revise, save the same kind and title with the old entry_id as supersedes_entry_id. The old version is kept; the newest of each kind and title is current.

A collab holds at most 30 current entries.

Response

The shape below is from the contract and the code (tools/save_event_context.py, event-context-contract.json). A success was not captured live, because this tool saves to a real collab.

Field	Meaning
`entry_id`	The saved entry.
`kind`, `title`	As saved.
`author`	`{kind, user_id}`.
`created_at`	When it was saved.
`supersedes_entry_id`	The entry it replaced, or null.
`body_chars`	The full length of the body.
`idempotent_replay`	true when this answer replays an earlier committed save.
`latest`	Every current entry the workspace holds on the collab, each with the fields above plus `body_preview` (the first 160 characters). Earlier versions are kept, not shown.

Rules the agent must follow

This tool changes nothing else. It never edits the collab’s description, its captured event details (date, location, hosts), its Playbook or its Luma event.
A company or person named in the text is never added as a partner or ABM account. Use manage_collab_partners for partners.
Do not put context into list names, event titles or any other field instead.
To revise, supersede. Never save a second entry with the same kind and title as if it replaced the first without supersedes_entry_id.
Only the workspace’s own collabs. A partner’s collab, the demo collab or an unknown id returns entity_not_found.

Errors and gaps

Code	What to do
`invalid_parameter`	Fix the named parameter and retry.
`entity_not_found`	Not one of the workspace’s own collabs.
`insufficient_scope`	The OAuth token lacks `mcp:tools:write`. Nothing was saved.
`internal_error`	Retry once with the SAME `client_request_id`.
429	Honor `Retry-After`. 30 requests per 5 s, 60 per minute, 1000 per day per workspace.

Trimmed from a real call with no arguments today:

{
  "tool": "save_event_context",
  "status": "error",
  "data": null,
  "error": {
    "code": "invalid_parameter",
    "what_failed": "A tool parameter (`channel_id`) is not valid for this tool.",
    "what_to_do": "Correct `channel_id` and retry.",
    "retryable": false
  }
}

update_collab, for the collab’s settings
get_event_details
activate_list, to send the invite you drafted
Playbook: Invite sprint

Get started

How heyBTW MCP works

Playbooks

Tools: orientation

Tools: events and rosters

Tools: people and invites

Tools: after the event

Tools: accounts and partners

Tools: pipeline

save_event_context

When to use it

Parameters

Workflow

Response

Rules the agent must follow

Errors and gaps

​When to use it

​Parameters

​Workflow

​Response

​Rules the agent must follow

​Errors and gaps

​Related

When to use it

Parameters

Workflow

Response

Rules the agent must follow

Errors and gaps

Related