Tools
get_view_alert_preview
Shows what one View would have emailed in the last 24 hours under your current settings, and sends nothing.
When to use it
- You just created or changed a View with
create_vieworupdate_viewand want to know what it will send. - You want to check your email mode and quiet hours on one View without waiting for real emails.
- You want the Matches the View recorded and whether each was sent: use
list_matches.
Inputs
view_id(uuid, required): The View to preview, fromlist_views.
Examples
If I leave my New York View as it is, how many emails will it send me?
{ "view_id": "2f1d7a4e-8c3b-4b9e-a6d5-0e9f8c7b6a51" }I just switched my Zach Bryan View to batched. What would it have sent in the last 24 hours?
{ "view_id": "7c9e6679-7425-40de-944b-e07fc1f90ae7" }What comes back
matches: the Matches the View caught in the window.emails: the emails those would have made, fewer thanmatcheswhen the View gathers them into onehourlyordailyemail.email_times, when each email would have gone, andfirst_email_at. The window iswindow_starttowindow_end.mode:instant,batchedormuted.pausedtrue: alert email is off for your whole account, so nothing would go out. The numbers show what turning it back on would send.quiet_hours_enabledtrue: sends inside your quiet hours were moved.lockwhen the View filters on a column your plan does not include:emailsis 0 until the account is onlock.required_tieragain.
Limits and quota
- Reads only: it changes nothing.
- Each call spends one MCP request.
- The window is the last 24 hours.
- It previews this one View. Your real email can carry Matches from several Views together, in fewer emails.
- Email only: destinations get each Match the instant it fires, whatever these settings say.