Your assistant sends your message by email and text to an event’s guests: those going, those who said maybe, those invited who have not answered, or everyone except people who declined. It is the same as the “message guests” button on the web, and your assistant should confirm the exact text and audience with you. UpTrust limits how often a message can go out, and guests can flag one as spam.
Ask it like this
- “Tell everyone going to the hike we are meeting at the north trailhead.”
- “Remind the people who have not answered about Saturday’s dinner.”
When another tool fits better
- Can you change my event?
The event itself changed.
Before you use it
- It needs the Create events and send invitations for you permission, which UpTrust asks you to approve when you connect.
- It writes to UpTrust, and part of what it does cannot be undone, such as notifications already sent or text it replaces. Its effects reach people or services beyond your own account.
- In Claude, connect
https://mcp.uptrusting.com/mcp. It is not on the ChatGPT address,https://mcp.uptrusting.com/chatgpt. How to connect.
What your assistant is told
Your assistant decides when to use this tool from the title and description UpTrust’s server gives it. Here they are exactly as the server sends them.
- Tool name
send_event_blast- Title
- Message an event's guests
- Description
Use this when the user asks to message, email or text the guests of an event they host or co-host. LOUD WRITE. It sends their message to those guests over email and SMS — the same blast the web "message guests" button sends. To change the event itself, use update_event. This is the commit point: confirm the exact message text AND the audience with the user before calling, and never send content the user did not write or approve. `audience` is required: `going`, `maybe`, `invited` (not yet responded), or `all` (everyone except declines). The backend enforces the product cadence — before the final hours, one blast per audience per 24 hours; near start time, a small last-minute budget for genuine changes — and recipients can flag a spammy blast, which costs the host future blast privileges. Treat a throttle rejection as "wait", not "retry".