Connector
Actions
10 actions, exposed as MCP tools. 7 only read; 3 change the account and carry a daily cap. Each page below is generated from the tool’s registration: the parameters table is the real input schema, and a test fails the build if a tool exists without a page or a page without a tool.
Read actions
Annotated readOnlyHint: true. Assistants call these without asking the operator first. No daily cap, only the per-minute request limit.
search_events
Search my events
The entry point for almost every workflow. Filter by part of the name, a date range or a status, and get back one row per event with its counts and gallery link. Take the id from here into the per-event tools.
Readget_event
Get one event
One event in full: the same row search_events returns, plus one entry per message with its number, source, state, length and whether the operator hid it. Use it when counts are not enough.
Readget_event_audio_status
Check audio status on an event
The cheapest way to answer "is the audio ready?" for one event: counts by state, a yes/no all_audio_ready flag and one short line per message. Smaller than get_event when you do not need durations or sources.
Readlist_events_needing_attention
List events that need a look
An account-wide "is anything stuck?" check: events with a message in needs_attention, or a message still cleaning more than 30 minutes after it arrived. An empty list means nothing needs the operator.
Readget_gallery_link
Get the gallery link
The share link for one gallery, on the operator's own domain when it is verified, plus whether guests need a share code to open it. The code itself is never returned.
Readget_gallery_stats
Get gallery stats
Visitors, plays and downloads for one gallery, whether it was sent, and the day it was first opened. Counts and dates only, from the same numbers the event page shows.
Readget_plan_and_usage
Get my plan and usage
Which plan the account is on, its subscription status and paid-through date, whether the free first event is used, and how many events exist. Call it before create_event when the assistant needs to say whether the next event will need payment.
Read
Write actions
Annotated readOnlyHint: false and destructiveHint: false: nothing here deletes. Claude and ChatGPT ask the operator to approve each call unless the operator turns that off. Every call is logged with the operator, the client, the action, the event and the time, and counted against the daily cap.
start_cleaning
Start cleaning an event
Runs Clean All on an event, exactly as the button on the event page does: every message that is not clean yet is sent to the cleaner. Idempotent: a second call while a run is in progress reports already_running and starts nothing.
Write30 per daycreate_event
Create an event
Creates an event with a name and an optional date, under the same rules as the dashboard: the free first event, an active subscription, or otherwise a locked event that waits for payment in the dashboard.
Write10 per dayupdate_event
Update event name or date
Changes the event name, the event date, or both. Nothing else about an event is reachable through the connector. Send null as the date to clear it.
Write50 per day