Email infrastructure for AI agents: send, read replies as threads, campaigns, per-key limits.
| Endpoint | https://mcp.sendraven.ai/mcp (streamable-http) |
|---|---|
| Registry version | 0.4.26 |
| Now | 63 tools · grade D (50) · pin ts_0d2eb7af46e3544892a1d8c2401680bc · protocol 2025-06-18 |
| First / last listed | 2026-10-31 02:28 UTC / 2026-10-31 02:28 UTC |
| Grade over time | 2026-10-31: D (50), 63 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: send_email list_emails get_email cancel_scheduled_email update_email_tags list_sending_domains add_sending_domain verify_sending_domain set_utm_tags list_suppressions add_suppression remove_suppression create_broadcast get_broadcast list_broadcasts preview_broadcast send_broadcast pick_broadcast_winner resume_broadcast list_threads get_thread reply_to_message mark_thread_handled list_templates render_template send_template_email list_pending_approvals decide_approval list_automations get_automation get_automation_metrics list_automation_enrollments create_automation update_automation set_automation_status delete_automation enroll_in_automation emit_event list_conversion_goals create_conversion_goal get_conversion_metrics list_topics get_email_preferences set_email_preferences list_audiences add_contact import_contacts get_contact update_contact list_segments list_tags count_segment get_email_metrics list_scheduled_emails suppress_many list_webhooks list_webhook_deliveries list_broadcast_recipients get_usage find_contact remove_from_audience delete_contact tag_contact
send_email | Send a transactional email, immediately or scheduled. scheduled_at takes a relative phrase like 'in 3 days' or an ISO timestamp. The From domain must already be verified. Every accepted send answers with the same fields: id, status, thread_id, scheduled_at, skipped, reason and approval_id. skipped: true (status 'rejected', with reason) means every recipient was suppressed or opted out and nothing params: from*, to*, cc, bcc, reply_to, subject*, html, text, scheduled_at, tags, idempotency_key |
list_emails | List messages newest first with their delivery status, including held, scheduled, skipped and failed ones and the mail campaigns and automations sent. Filter by status, recipient or tag. Paged: at most 100 per call; while has_more is true, next_cursor passed back as cursor with the same filters returns the next page. An unknown status is refused with 422 invalid_request rather than answering an em params: status, to, tag, limit, cursor |
get_email | Fetch one message with its full event timeline (send, delivery, bounce, complaint, open, click). The timeline shows why an email didn't arrive. params: id* |
cancel_scheduled_email | Cancel a scheduled email before it sends. Only works while status is 'scheduled': a message that has already started sending, or is in any other state, answers 409 invalid_state naming its status; a retry answers the same, and get_email shows where it stands. An unknown id answers 404 not_found. params: id* |
update_email_tags | Add or remove tags on an email already sent, scheduled or held, to refile it for the tag filters of list_emails and list_threads. Removals apply first, then additions, so one call swaps a tag: remove_tags [{name:'recovery_case'}] (no value: every tag with that name) with add_tags [{name:'category', value:'billing-recovery'}]. The thread and the dashboard's tag suggestions follow. Changes only what params: id*, add_tags, remove_tags |
list_sending_domains | List sending domains with their verification status and the DNS records each one needs. Each record shows what is currently published, so this diagnoses a stuck verification. mail_from says whether SES has adopted the bounce. subdomain as the Return-Path: pending while SES polls for its MX record, then active. SES polls for 72 hours from when the domain was added, not from when the MX appears, and params: none |
add_sending_domain | Register a sending domain and get back the DNS records to publish. It takes the domain mail is sent from — mail.<domain> and news.<domain> are provisioned beneath it and the right one is chosen per message, so a marketing complaint spike can never affect password reset delivery. subdomains names the pair differently (tx. and promo.), still one domain. risk_class provisions one identity on the doma params: domain*, risk_class, subdomains |
verify_sending_domain | Re-check a domain's DNS records now instead of waiting for the background monitor. Also restarts bounce-path (mail_from) verification when SES gave up before the MX record existed. params: id* |
set_utm_tags | Turn UTM tags on or off for a sending domain, and set what they say. When on, every link in that domain's marketing HTML gets utm_source (default 'newsletter'), utm_medium (default 'email') and utm_campaign (the campaign's name or the automation's slug). A link that already has any utm_ parameter is left as written, and unsubscribe links are never touched. Fields left out keep their value; a null params: id*, enabled, source, medium, include_transactional, hosts |
list_suppressions | List addresses we refuse to mail and why (hard_bounce, complaint, unsubscribe, manual, list_hygiene), newest first, each with its scope. When someone reports not receiving email, this shows whether the address is suppressed. email returns one address's suppressions directly; scanning pages instead is how the wrong suppression gets cleared. At most 100 per call; while has_more is true, next_cursor params: email, limit, cursor |
add_suppression | Stop sending to an address. Scope 'marketing' leaves transactional mail working; the default is 'all'. Reason 'unsubscribe' is a real opt-out: it also cancels the person's queued scheduled sends and ends their automation enrolments, which is what a person who asked to stop expects and 'manual' does not do. A hard bounce or complaint already on file is never replaced; the response is the stored sup params: email*, scope, reason |
remove_suppression | Remove a suppression so the address can be mailed again. A hard bounce means the address was rejected by the receiving server, and re-sending raises the bounce rate that AWS enforces on. The scope must match the stored one: removed: false means nothing was suppressed in that scope (an address suppressed for 'marketing' is not lifted by 'all'); list_suppressions with email shows the scope that is s params: email*, scope |
create_broadcast | Create a campaign as a draft. Nothing is sent: preview_broadcast reports its reach and send_broadcast sends it. identity_id must be a marketing sending domain (see list_sending_domains; risk_class 'marketing'). topic_key must name an existing topic (list_topics); an unknown one is refused with 422 unknown_topic, since it would count everyone as opted out. A segment_id must filter the same audience params: audience_id*, identity_id*, name*, subject*, html*, from_name, topic_key, view_in_browser, segment_id, segment, variants, ab_test |
get_broadcast | One campaign, with a 'progress' object while it is sending, paused or testing: how many addresses are still pending, sent, failed, or skipped because the person opted out after the campaign started. This is what tells a paused campaign that is still making progress from one that is waiting; pause_reason says on what, and resume_after when a warm-up pause renews. progress is null for a campaign not params: id* |
list_broadcasts | List campaigns, newest first, with their status. Paged: at most 100 per call; while has_more is true, next_cursor passed back as cursor returns the next page. Each row is the campaign object get_broadcast returns, live progress and A/B results included, without its html, which only get_broadcast returns. Every field is snake_case and always present, null when unset. A campaign showing 'paused' is params: limit, cursor |
preview_broadcast | How many contacts a campaign would reach, and whether the reputation gate would allow it. It is the only way to see the size of a campaign without starting it. For an A/B test it also reports the sample size and per-variant count against the 100-per-variant floor; a send below the floor is refused. params: id* |
send_broadcast | Send a draft or scheduled campaign now, or schedule it with scheduled_at. This mails every contact in the segment and cannot be undone once started; preview_broadcast shows the count beforehand. Marketing mail must carry a postal address: a workspace without one is refused with 422 no_postal_address (a person adds it in Settings), and a suspended workspace with 422 workspace_suspended, whether sen params: id*, scheduled_at |
pick_broadcast_winner | Decide an A/B test now instead of waiting for decide_at. 'variant' names the winning key; without it the metric decides on the figures so far. The rest of the audience is then sent to the winner and cannot be redirected. Only a campaign in status 'testing' can be decided; anything else, or a campaign that is not an A/B test, answers 409 invalid_state. A variant key the campaign does not have answe params: id*, variant |
resume_broadcast | Continue a paused campaign now. It mails only the addresses still pending — the audience was frozen when the campaign started and everyone already reached is marked — so calling this twice cannot double-send. Only works on a paused campaign; anything else answers 409 invalid_state. pause_reason says why it paused. A background worker resumes quota, interrupted and suspension pauses on its own, so params: id* |
list_threads | List email conversations. awaiting_reply=true returns only the threads where someone has written in and no answer has been sent, which is what needs a response. A reply held for approval or scheduled does not count as sent: such a thread stays in that list with pending_reply true, meaning its answer is already on the way. Most recently active first, at most 100 per call; while has_more is true, ne params: awaiting_reply, tag, limit, cursor |
get_thread | Read a conversation as a chronological transcript of outbound and inbound messages. Inbound `text` already has quoted history and signatures stripped; `raw_text` holds the untrimmed body, for when the stripped version looks wrong. sender_authenticated says whether the sender is who the From line claims; when false the From line may be forged, and a forged sender still passes SPF, so spf_verdict do params: id* |
reply_to_message | Reply to a message, keeping it on the same conversation. Sets the threading headers so the recipient's mail client shows it as part of the existing exchange rather than a new one, which send_email does not do. It is a send, so it answers exactly as send_email does and meets the same refusals (422 no_verified_identity, 429 daily_limit, 403 recipient_not_allowed, and so on); idempotency_key makes a params: reply_to_message_id*, from*, to*, subject*, text, html, scheduled_at, tags, idempotency_key |
mark_thread_handled | Clear a conversation's awaiting_reply flag without sending anything, for when the last inbound message needs no answer — a "thanks, all sorted" — so it stops appearing in list_threads with awaiting_reply=true. A reply sent only to clear the flag mails a person for bookkeeping; this clears it without one. The next message they send flags the thread again. params: id* |
list_templates | List stored email templates and the variables each one needs. Unlike HTML composed at send time, templates carry the workspace's reviewed subject, copy and styling. They do not carry the unsubscribe footer: that is added at send time to marketing mail, whether or not it came from a template. params: none |
render_template | Render a template with values, without sending, showing how the copy reads before it mails a real person. A missing variable answers 422 missing_variables with the list in `missing`; an unknown slug answers 404. Returns subject, html and text; text is null when the template has no plain-text part. params: slug*, variables* |
send_template_email | Send an email built from a stored template. Variable values are HTML-escaped on substitution, so they are safe to fill from user-supplied text. Nothing is sent when a value is missing: 422 missing_variables lists the names in `missing`, and a call with those filled in goes through (render_template checks this without sending). An unknown slug answers 422 invalid_request. The response has the same params: template*, variables*, from*, to*, reply_to, subject, scheduled_at, idempotency_key |
list_pending_approvals | List messages held for human approval, with their full content. A key configured to require approval drafts rather than sends; a person releases it. A send that returned status 'pending_approval' is waiting here, and retrying the send does not release it. Oldest first, each with its expires_at; an expired approval drops out of the list and can no longer be decided. params: none |
decide_approval | Approve or reject a held message. Approving releases it: it sends now, or at its scheduled_at when the draft was scheduled for later. If every recipient unsubscribed or was suppressed while it waited, nothing is sent and the answer says skipped: true with a reason (both always present: false and null otherwise, beside scheduled_at). The approval hold exists so that a person, not an agent, makes th params: id*, decision*, decided_by*, reason |
list_automations | List multi-step email sequences and how many people are currently in each, with the id each one is enrolled by. Newest first, at most 100 per call; while has_more is true, next_cursor passed back as cursor returns the next page. A 'paused' automation holds its people on their current step rather than ending their sequence: they stay 'active' and continue from that step once it is active again. lis params: limit, cursor |
get_automation | Fetch one automation: its status, trigger, steps (each with the id and condition update_automation needs passed back), exit rules and how many people are in each state. The same object list_automations returns, for a caller that already holds the id. People themselves are listed by list_automation_enrollments, and per-step opens and clicks by get_automation_metrics. An unknown automation_id answer params: automation_id* |
get_automation_metrics | How each step of an automation is doing: per current step, its step_id, position, sent, delivered, opened and clicked. Opens and clicks are unique people, counted only after link scanners are ruled out, so they are lower than raw hit counts and reflect readers. Use it to see where a sequence loses people or which step to rewrite; list_automations has only enrolment counts. A step's figures follow params: automation_id* |
list_automation_enrollments | The people in one automation, newest enrolment first: each row has the email, status, current_step, next_due_at and, for a cancelled one, cancel_reason. It answers 'is this person still on the sequence?', 'who is waiting on step 2?' and 'why did this sequence stop for them?', which find_contact and list_emails do not. status narrows to one state: 'active' (still going, including people held while params: automation_id*, status, limit, cursor |
create_automation | Define a multi-step sequence as a draft; nothing is sent until it is activated, from the dashboard or with set_automation_status. Unlike several separately scheduled emails, it ends on its own when the person unsubscribes, replies, bounces, opts out of its topic, or their tags say so. identity_id must be a marketing sending domain (see list_sending_domains; risk_class 'marketing') and from must si params: name*, slug*, identity_id*, from*, reply_to, trigger*, steps*, topic_key, exit_tags, required_tags, exit_on_reply, reenrollment, default_variables |
update_automation | Change a sequence's steps, the rules that take someone out of it (topic_key, exit_tags, required_tags, exit_on_reply), its reply_to, its reenrollment, or its default_variables (replaces the whole set; {} clears it). The trigger is fixed once created. steps replaces every step and is safe on a live automation only when each step you keep is passed back with the id get_automation returned: people on params: automation_id*, topic_key, exit_tags, required_tags, exit_on_reply, reply_to, reenrollment, default_variables, steps |
set_automation_status | Activate, pause or return an automation to draft. A new automation is a draft and sends nothing until it is set to 'active'. Pausing ('paused' or 'draft') holds everyone on their current step: nobody is sent a step and nobody new is enrolled, but nobody's sequence ends, and setting 'active' again continues each person from where they were, with steps that came due meanwhile going out from the next params: automation_id*, status* |
delete_automation | Delete an automation for good and cancel every active enrolment in it, so nobody is sent another step. Answers enrollments_canceled. It cannot be undone: to stop it for a while and continue everyone later, use set_automation_status with paused instead. Mail already sent and its history stay. params: automation_id* |
enroll_in_automation | Put someone into a multi-step sequence. Unlike several separately scheduled emails, the sequence stops on its own if they unsubscribe (from everything or from the automation's topic), reply, hard bounce, gain one of its exit tags, or lose one of its required tags, which would otherwise have to be tracked and cancelled by hand. A sequence stops for someone who converted when the contact is tagged w params: automation_id*, email*, variables |
emit_event | Emit a named event, starting every automation that waits on it — for example 'trial_started' or 'invoice_overdue'. The configured sequences decide what happens, rather than the caller naming an automation. Returns automations_started; 0 means nothing was waiting on that name or the person was excluded. The calling key's guardrails apply as for enroll_in_automation, before anything is looked up: a params: name*, email*, variables, id, value, currency |
list_conversion_goals | List conversion goals: the event names counted as a conversion, each with its credit window in days. An emit_event call with one of these names is credited to the last email the person clicked inside that window; any other name is an ordinary event. params: none |
create_conversion_goal | Start counting an event as a conversion, such as 'subscription_started' or 'purchase'. Counts only events emitted after this call; it does not go back over earlier ones. Use the exact name the app already passes to emit_event. A name that is already a goal answers 409 conflict, and list_conversion_goals has its id. params: event_name*, window_days |
get_conversion_metrics | Attributed conversions, converters and revenue per currency. Pass broadcast_id for a campaign, broken down per A/B variant with its sent count and rate, or automation_id for a sequence, broken down per step. The figures are attributed, not causal: each conversion counts for the last email its person clicked, and scanner clicks and opens never count. The rate is people over messages sent. A convers params: broadcast_id, automation_id, goal_id, from, to |
list_topics | List subscription topics — the categories a person can opt out of individually. Marketing mail sent under a topic lets recipients unsubscribe from that kind alone rather than from everything. params: none |
get_email_preferences | What one person has chosen to receive. It shows whether someone who isn't getting a particular kind of email opted out of it — an opt-out looks identical to a delivery failure from the outside. params: email* |
set_email_preferences | Set which topics a person receives, recording what they asked for — silently re-subscribing someone who opted out is what generates spam complaints. Every key must be an existing topic from list_topics: one unknown key refuses the whole call with 422 unknown_topic and nothing is saved. Setting a topic to false also ends any automation enrolment sent under that topic. params: email*, topics* |
list_audiences | List contact lists, newest first, with each one's id and contact_count. Paged: at most 100 per call; while has_more is true, more lists are on later pages, returned when next_cursor is passed back as cursor. params: limit, cursor |
add_contact | Add someone to an audience. A contact exists once per workspace and can be on any number of audiences, so adding an address that already exists joins them to this list rather than creating a second copy. status records that the person opted out elsewhere — it writes the suppression as well as the flag, and an add never resubscribes someone who opted out here. Someone new to the audience starts any params: audience_id*, email*, first_name, last_name, tags, attributes, status, last_active_at |
import_contacts | Import up to 5,000 contacts into an audience in one call, with names, tags, custom properties and subscription status. This is the migration tool: the previous provider's unsubscribed, bounced and complained lists, imported with the matching status before the first campaign, keep the new domain from mailing people who opted out, which loses a domain its reputation in a day. Existing contacts are u params: audience_id*, contacts*, source, trigger_automations |
get_contact | Fetch one contact by id, with their audience memberships, custom properties and engagement dates. params: id* |
update_contact | Update a contact. Attributes are merged, so sending one field does not clear the rest. unsubscribed: true is a real opt-out: it suppresses the address for marketing, cancels their pending sends and ends their automation enrolments. unsubscribed: false lifts a marketing unsubscribe, which is for a person who asked to be resubscribed. Resubscribing someone who hard bounced or complained is refused w params: id*, first_name, last_name, unsubscribed, attributes, last_active_at |
list_segments | List saved audience filters. A campaign created with a segment id, rather than a filter described inline, shares one definition that can be reused and counted. params: none |
list_tags | Every tag in use in the workspace, with how many contacts carry each. Tags are free-form, so this is the only way to know what exists before applying one. params: none |
count_segment | How many contacts a segment currently matches. A filter that matches nobody shows up here as 0, before any campaign is built around it or sent. Engagement windows and date conditions (e.g. attributes.trial_ends_at within_next_days 3) are measured from the moment of the call, so the count of the same segment moves from day to day. params: id* |
get_email_metrics | Delivery and engagement over a window. Open and click rates are over delivered, not sent — a low open rate with a high bounce rate is a deliverability problem, not an engagement one. params: days |
list_scheduled_emails | Messages queued to send later but not yet sent, newest first; cancel_scheduled_email cancels one. At most 100 per call; while has_more is true, next_cursor passed back as cursor returns the next page. params: limit, cursor |
suppress_many | Stop sending to many addresses at once — the path for importing another provider's unsubscribe list before a first campaign. Without it, everyone who already opted out there gets mailed again here. The defaults differ from add_suppression: scope 'marketing' and reason 'list_hygiene'. reason 'unsubscribe' marks a list of opt-outs, and also cancels their queued scheduled sends and ends their automat params: emails*, scope, reason |
list_webhooks | The workspace's webhook endpoints: each with id, url, the events it receives and whether it is enabled. Read-only: endpoints are added and changed in the dashboard, because a tool that could point one at a new URL would let an agent route the workspace's mail events to itself. Use an id here with list_webhook_deliveries. params: limit, cursor |
list_webhook_deliveries | Recent delivery attempts for a webhook endpoint: each with event, status, attempts, last_status_code, last_error and delivered_at (null until it succeeds). This is what tells 'we never sent it' from 'your endpoint returned 500'. Newest first, the most recent `limit` only; not paged. params: endpoint_id*, limit |
list_broadcast_recipients | Who a campaign reached and what happened to each message, with the A/B variant when there is one. At most 200 per call; while has_more is true, next_cursor (a message id) passed back as cursor returns the next page. params: id*, limit, cursor |
get_usage | This workspace's plan, what it has sent this billing period, what the period costs so far, and — the fields worth branching on — sending_locked and lock_reason, which name the exact 402 a send would be refused with right now, before a large batch or campaign is tried: on Free a send that would cross the 3,000 included emails is refused whole, and a workspace with no verified payment method cannot params: none |
find_contact | Find a contact by address across every audience, without knowing which list they are on, or list the workspace's contacts by tag or subscription. email matches exactly, and q matches an address prefix. A person exists once per workspace, so each row is one contact with audience_ids listing every list they are on, first_name, last_name, tags, attributes and whether they are unsubscribed. Newest fir params: email, q, tag, unsubscribed, limit, cursor |
remove_from_audience | Take a contact off one audience. They stay in the workspace and keep every other audience, their suppression and their engagement history. delete_contact removes the person entirely — leaving a list and being forgotten are different things. params: audience_id*, contact_id* |
delete_contact | Remove a person from the workspace entirely, along with every audience membership. Their suppression and topic preferences are kept on purpose — an opt-out has to outlive the contact record, or the next import silently puts them back on the list. remove_from_audience takes someone off a single audience instead. params: contact_id* |
tag_contact | Add or remove tags on a contact. Tags are flat labels — vip, beta, churned — as opposed to custom properties, which are declared fields with a value. They are lower-cased and spaces become hyphens, so VIP and vip are the same tag. Tagging reaches the person across every audience they are on. list_tags returns the tags the workspace already uses, so an existing tag can be reused rather than a synon params: contact_id*, add, remove |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.