Servidor MCP
Hail
io.github.hail-hq/hail-mcp
Qué hace este MCP
Manages contacts and sends, receives, tracks, and retrieves phone calls, SMS messages, and emails.
Capacidades
Herramientas
20
herramientas
create_contact
Save a new contact for the workspace. Provide at least one of
``phone_e164`` (E.164, e.g. ``+14155551234``) or ``email`` â the API
rejects (422) a contact with neither. A duplicate phone or email on
an existing contact returns 409.
Example:
create_contact(name="Maya Chen", phone_e164="+14155551234")
Returns the created contact entry as a dict. On failure returns
``{"error": "<message>"}`` instead.
Esquema de entrada
{'type': 'object', 'title': 'create_contact_toolArguments', 'required': ['name'], 'properties': {'name': {'type': 'string', 'title': 'Name'}, 'email': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Email', 'default': None}, 'phone_e164': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Phone E164', 'default': None}}}
Esquema de salida
{'type': 'object', 'title': 'create_contact_toolDictOutput', 'additionalProperties': True}
get_call
Fetch the current state of one call by id.
Use this after ``place_call`` (or to check on any prior call)
to read the call's latest ``status`` and timing fields.
Returns the API's ``CallResponse`` as a dict, or
``{"error": "call not found"}`` for an unknown id.
Esquema de entrada
{'type': 'object', 'title': 'get_call_toolArguments', 'required': ['call_id'], 'properties': {'call_id': {'type': 'string', 'title': 'Call Id'}}}
Esquema de salida
{'type': 'object', 'title': 'get_call_toolDictOutput', 'additionalProperties': True}
get_email
Fetch the full record of one email by id.
Returns the complete row â including ``body_text`` / ``body_html``
and (for inbound mail) the ``in_reply_to`` / ``message_id`` headers
and ``spam``/``virus``/``spf``/``dkim``/``dmarc`` verdicts. Use this
after ``list_emails`` to read a received reply's body.
Returns the API's ``EmailResponse`` as a dict, or
``{"error": "resource not found"}`` for an unknown id.
Esquema de entrada
{'type': 'object', 'title': 'get_email_toolArguments', 'required': ['email_id'], 'properties': {'email_id': {'type': 'string', 'title': 'Email Id'}}}
Esquema de salida
{'type': 'object', 'title': 'get_email_toolDictOutput', 'additionalProperties': True}
get_email_attachment
Get a fetchable URL for one inbound email attachment.
``attachment_id`` comes from an item in ``get_email``'s
``attachments`` list. Returns ``{"url": "<presigned-s3-url>"}`` â
a short-lived (~5 minute) link to the attachment bytes, fetchable
directly with no auth header. Unknown ids return
``{"error": "resource not found"}``.
Esquema de entrada
{'type': 'object', 'title': 'get_email_attachment_toolArguments', 'required': ['email_id', 'attachment_id'], 'properties': {'email_id': {'type': 'string', 'title': 'Email Id'}, 'attachment_id': {'type': 'string', 'title': 'Attachment Id'}}}
Esquema de salida
{'type': 'object', 'title': 'get_email_attachment_toolDictOutput', 'additionalProperties': True}
get_email_events
Delivery/engagement timeline (sentâdeliveredâopenedâ¦) for one email.
Chronological lifecycle events for a single email â use this to see
exactly what happened to one message (bounced? opened? clicked?)
rather than the account-wide aggregates ``get_email_stats`` returns.
Returns ``{"items": [...], "next_cursor": ...}`` where each item has
``kind`` (one of sent, delivered, delivery_delayed, bounced,
complained, rejected, opened, clicked), ``payload``, and
``occurred_at``. ``opened`` and ``clicked`` only occur for emails
sent with an HTML body. A plain-text-only email still gets sent,
delivered, and bounce events, but opens and clicks are never
tracked. Pass ``cursor`` from a previous ``next_cursor`` to
page (``limit`` 1..1000, default 100). On failure returns
``{"error": "resource not found"}`` for an unknown id.
Esquema de entrada
{'type': 'object', 'title': 'get_email_events_toolArguments', 'required': ['email_id'], 'properties': {'limit': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Limit', 'default': None}, 'cursor': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Cursor', 'default': None}, 'email_id': {'type': 'string', 'title': 'Email Id'}}}
Esquema de salida
{'type': 'object', 'title': 'get_email_events_toolDictOutput', 'additionalProperties': True}
get_email_raw
Get a fetchable URL for an email's original MIME source.
Returns ``{"url": "<presigned-s3-url>"}`` â a short-lived
(~5 minute) link to the full raw RFC822 message. Fetch the URL
directly to read the complete original; it needs no auth header.
Raw source exists for **inbound** mail only â outbound ids return
``{"error": "resource not found"}``.
Esquema de entrada
{'type': 'object', 'title': 'get_email_raw_toolArguments', 'required': ['email_id'], 'properties': {'email_id': {'type': 'string', 'title': 'Email Id'}}}
Esquema de salida
{'type': 'object', 'title': 'get_email_raw_toolDictOutput', 'additionalProperties': True}
get_email_stats
Account-level email deliverability stats (counts, rates, time series).
Aggregates across your whole organization's outbound mail over a
window â use this for "how's deliverability doing" rather than
one message's history (``get_email_events`` covers that).
``from_`` / ``to`` are ISO 8601 timestamps (defaults: last 7 days
ending now). ``bucket`` is ``"day"`` (default) or ``"hour"`` â
``"hour"`` is limited to an 8-day span; any range is capped at 92
days.
Returns ``{"from": ..., "to": ..., "bucket": ..., "totals": {...},
"rates": {...}, "series": [...]}`` â ``totals``/each ``series``
bucket carry counts (sent, delivered, bounced, opened, ...) and
``rates`` carries derived ratios (delivery, bounce, open, click),
each ``None`` when ``totals.sent`` is 0. Open and click numbers
only count HTML emails. Plain-text-only emails are never tracked
for opens or clicks, so they lower those rates. On failure returns
``{"error": "<message>"}`` instead.
Esquema de entrada
{'type': 'object', 'title': 'get_email_stats_toolArguments', 'properties': {'to': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'To', 'default': None}, 'from_': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'From', 'default': None}, 'bucket': {'type': 'string', 'title': 'Bucket', 'default': 'day'}}}
Esquema de salida
{'type': 'object', 'title': 'get_email_stats_toolDictOutput', 'additionalProperties': True}
get_events
Page through events from across the org or one resource.
Pass ``id="<type>:<uuid>"`` to narrow to a single resource â
supported types are ``call``, ``email``, and ``sms`` (e.g.
``id="sms:<uuid>"`` after ``send_sms``). When narrowed to a
call, the response includes a ``call_status`` field reflecting
the call's current state. Without ``id``, returns events from
across the whole org. ``kind`` filters server-side by event kind
(``state_change``, ``agent_turn``, ``user_turn``, ``tool_call``,
``error``, ...).
This is **not** a streaming subscription â the call returns
whatever events exist now plus a ``next_cursor`` if more pages
remain. To follow a call to completion, loop: pass the previous
response's ``next_cursor`` until ``next_cursor`` is null and,
when narrowed to a call, ``call_status`` is one of
``completed``, ``failed``, ``busy``, ``no_answer``, ``canceled``
(the terminal set).
Example:
get_events(id="call:0c2f...-...", limit=200)
Returns ``{"items": [...], "next_cursor": <str|None>,
"call_status": <str|None>}`` on success, or
``{"error": ...}`` on a malformed ``id`` or upstream failure.
Esquema de entrada
{'type': 'object', 'title': 'get_events_toolArguments', 'properties': {'id': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Id', 'default': None}, 'kind': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Kind', 'default': None}, 'limit': {'type': 'integer', 'title': 'Limit', 'default': 100}, 'cursor': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Cursor', 'default': None}}}
Esquema de salida
{'type': 'object', 'title': 'get_events_toolDictOutput', 'additionalProperties': True}
get_sms
Fetch the current state of one SMS by id.
Use this after ``send_sms`` to check delivery status.
Example:
get_sms(sms_id="...")
Esquema de entrada
{'type': 'object', 'title': 'get_sms_toolArguments', 'required': ['sms_id'], 'properties': {'sms_id': {'type': 'string', 'title': 'Sms Id'}}}
Esquema de salida
{'type': 'object', 'title': 'get_sms_toolDictOutput', 'additionalProperties': True}
list_calls
List recent calls in your organization, newest first.
Cursor-paginated: pass the previous response's ``next_cursor``
to fetch the next page. ``status`` (one of queued, dialing,
ringing, in_progress, completed, failed, busy, no_answer,
canceled) and ``to`` (E.164) are optional server-side filters.
Returns a dict ``{"items": [...], "next_cursor": <str|None>}``.
Esquema de entrada
{'type': 'object', 'title': 'list_calls_toolArguments', 'properties': {'to': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'To', 'default': None}, 'limit': {'type': 'integer', 'title': 'Limit', 'default': 50}, 'cursor': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Cursor', 'default': None}, 'status': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Status', 'default': None}}}
Esquema de salida
{'type': 'object', 'title': 'list_calls_toolDictOutput', 'additionalProperties': True}
list_contacts
List the workspace's contacts: org members (with their phone/email)
plus manually saved contacts. Use ``lookup_contact`` for name searches.
``q`` optionally filters server-side (matches name/email/phone).
``limit`` caps the page (server default 100, max 500).
Returns ``{"items": [{"id", "kind", "name", "phone_e164", "email",
"role"}, ...]}`` â ``kind`` is ``"member"`` (id ``member:<user_id>``,
``role`` set) or ``"manual"`` (id is the contact's UUID, ``role``
null).
Esquema de entrada
{'type': 'object', 'title': 'list_contacts_toolArguments', 'properties': {'q': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Q', 'default': None}, 'limit': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Limit', 'default': None}}}
Esquema de salida
{'type': 'object', 'title': 'list_contacts_toolDictOutput', 'additionalProperties': True}
list_email_domains
List the addresses this workspace can send email from. Call this
BEFORE ``send_email`` when you do not already know the ``from_``
address â do not guess a domain.
Returns ``{"items": [...], "next_cursor": ..., "default_from": ...}``.
Each item carries ``domain``, ``kind`` (``"custom"`` or
``"hail_mail"``) and ``verification_status``; only ``"verified"``
rows can send. A ``custom`` item's ``domain`` is a bare DNS name
that accepts any local-part (``sales@acme.com``); a ``hail_mail``
item's ``domain`` is already a full address.
``default_from`` is the address a ``send_email`` with no ``from_``
goes out as. It is null when the workspace has several verified
identities â then ``send_email`` rejects a missing ``from_`` and you
must pass one from ``items``.
Example:
list_email_domains()
Esquema de entrada
{'type': 'object', 'title': 'list_email_domains_toolArguments', 'properties': {'limit': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Limit', 'default': None}, 'cursor': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Cursor', 'default': None}}}
Esquema de salida
{'type': 'object', 'title': 'list_email_domains_toolDictOutput', 'additionalProperties': True}
list_emails
List emails in your organization, newest first.
Cursor-paginated: pass the previous response's ``next_cursor`` to
fetch the next page. Two optional server-side filters:
* ``direction`` â ``outbound`` or ``inbound``. Pass
``direction="inbound"`` to read replies and other received mail.
* ``status`` â one of ``queued``, ``sent``, ``failed``,
``bounced``, ``complained``, ``received``.
Items are trimmed summaries (no message body). Call ``get_email``
with an item's ``id`` to read the full body.
Example:
list_emails(direction="inbound")
Returns ``{"items": [...], "next_cursor": <str|None>}`` on success,
or ``{"error": "<message>"}`` instead.
Esquema de entrada
{'type': 'object', 'title': 'list_emails_toolArguments', 'properties': {'limit': {'type': 'integer', 'title': 'Limit', 'default': 50}, 'cursor': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Cursor', 'default': None}, 'status': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Status', 'default': None}, 'direction': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Direction', 'default': None}}}
Esquema de salida
{'type': 'object', 'title': 'list_emails_toolDictOutput', 'additionalProperties': True}
list_sms
Page through recent SMS messages for your organization.
``status`` filters to one of: queued, sent, delivered, failed,
undelivered, received. ``to`` filters to messages sent to a
specific E.164 number. Paginate with the returned
``next_cursor``.
Esquema de entrada
{'type': 'object', 'title': 'list_sms_toolArguments', 'properties': {'to': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'To', 'default': None}, 'limit': {'type': 'integer', 'title': 'Limit', 'default': 50}, 'cursor': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Cursor', 'default': None}, 'status': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Status', 'default': None}}}
Esquema de salida
{'type': 'object', 'title': 'list_sms_toolDictOutput', 'additionalProperties': True}
lookup_contact
Find a contact by name, email, or phone fragment. Resolve a person
to their ``phone_e164``/``email`` BEFORE calling ``place_call``,
``send_sms``, or ``send_email`` â do not guess a contact's number.
Returns up to 10 matches, same item shape as ``list_contacts``.
Example:
lookup_contact(query="maya")
Esquema de entrada
{'type': 'object', 'title': 'lookup_contact_toolArguments', 'required': ['query'], 'properties': {'query': {'type': 'string', 'title': 'Query'}}}
Esquema de salida
{'type': 'object', 'title': 'lookup_contact_toolDictOutput', 'additionalProperties': True}
place_call
Originate an outbound phone call.
Provide ``system_prompt`` (mode A â Hail's bundled fallback LLM
uses this prompt) or ``llm`` (mode B â bring your own
OpenAI-compatible endpoint as
``{"base_url": ..., "api_key": ..., "model": ...}``), or both.
At least one is required. Passing both runs your prompt on your
own endpoint: it receives Hail's voice preamble plus your prompt
as the leading system message.
``to`` must be E.164 (e.g. ``+14155551234``). ``from_`` is
optional and defaults to the first active number on your org.
``first_message`` is spoken verbatim on pickup; omit it to let
the agent open the conversation itself â it reacts to how the
call was answered, or introduces itself after silence.
``language`` sets the call's spoken language for speech-to-text,
text-to-speech, and turn detection, as a lowercase ISO 639-1 code
(e.g. ``"da"``); 39 languages are supported (server rejects others
with 422); omit for English. STT provider selection is
console-BYO-only (no per-call override); configure it on the
organization to pin a provider.
``ai_disclosure=False`` skips the spoken "this is an AI
assistant" line at the start of the call. Leave enabled unless
the user has verified it is not required for this call â US
artificial-voice calls (47 CFR 64.1200(b)(1)) and several AI
bot-disclosure laws require it, and Hail does not verify this.
The agent still identifies itself as an AI if asked.
``metadata`` is free-form JSON attached to the call record.
``tools`` are the agent tools to allow on this call. Omit for all
available; pass ``[]`` to disable.
``recipient_consent`` is required: attest that you (the caller
triggering this request) have obtained the lawful consent needed
to contact this recipient. The API rejects the request (422) if
this is not ``true`` â Hail does not verify consent for you, you
are responsible for having a lawful basis (TCPA / ePrivacy / GDPR
as applicable). Set ``message_type="marketing"`` for promotional
calls (this additionally requires a non-empty ``consent_source``
describing how/where consent was obtained) â leave as the default
``"informational"`` for transactional/service calls.
``idempotency_key`` defaults to a fresh UUID per invocation
and is returned in the response under ``idempotency_key`` â to
retry *this* exact request (rather than dispatch a second call),
pass the value back on the retry. A new key is a new call.
Example:
place_call(to="+14155551234",
recipient_consent=True,
system_prompt="You are scheduling a haircut.",
first_message="Hi, I'm calling on behalf of Alex.")
Returns the API's ``CallResponse`` as a dict (id, status,
from_e164, to_e164, ...). On failure returns
``{"error": "<message>"}`` instead.
Esquema de entrada
{'type': 'object', 'title': 'place_call_toolArguments', 'required': ['to', 'recipient_consent'], 'properties': {'to': {'type': 'string', 'title': 'To'}, 'llm': {'anyOf': [{'type': 'object', 'additionalProperties': True}, {'type': 'null'}], 'title': 'Llm', 'default': None}, 'from_': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'From', 'default': None}, 'tools': {'anyOf': [{'type': 'array', 'items': {'type': 'string'}}, {'type': 'null'}], 'title': 'Tools', 'default': None}, 'language': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Language', 'default': None}, 'metadata': {'anyOf': [{'type': 'object', 'additionalProperties': True}, {'type': 'null'}], 'title': 'Metadata', 'default': None}, 'message_type': {'type': 'string', 'title': 'Message Type', 'default': 'informational'}, 'ai_disclosure': {'type': 'boolean', 'title': 'Ai Disclosure', 'default': True}, 'first_message': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'First Message', 'default': None}, 'system_prompt': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'System Prompt', 'default': None}, 'consent_source': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Consent Source', 'default': None}, 'idempotency_key': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Idempotency Key', 'default': None}, 'recipient_consent': {'type': 'boolean', 'title': 'Recipient Consent'}, 'consent_obtained_at': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Consent Obtained At', 'default': None}}}
Esquema de salida
{'type': 'object', 'title': 'place_call_toolDictOutput', 'additionalProperties': True}
send_email
Send an outbound email through your configured SES sender.
``to`` is a non-empty list of RFC-style email addresses. At
least one of ``body_text`` / ``body_html`` is required (both
is fine â multipart-alternative). Prefer including
``body_html``: open and click tracking only works for emails
with an HTML body. A plain-text-only email still gets sent,
delivered, and bounce events, but opens and clicks are never
tracked. ``cc``, ``bcc``, and
``reply_to`` are optional and follow the usual mail
conventions. Hail sets no ``reply_to`` of its own â to have
replies reach the human running this session, call ``whoami``
and pass their ``email``.
``recipient_consent`` is required: attest that you (the caller
triggering this request) have obtained the lawful consent needed
to email this recipient. The API rejects the request (422) if
this is not ``true`` â Hail does not verify consent for you. Set
``message_type="marketing"`` for promotional email (this
additionally requires a non-empty ``consent_source`` describing
how/where consent was obtained) â leave as the default
``"informational"`` for transactional/service email.
``from_`` is optional only while the workspace has one verified
sender identity. With several, omitting it returns 422 listing
them â call ``list_email_domains`` and pass one. With none, the
server auto-mints a per-org hail-mail address of the form
``<user>+<org>@<base>`` if the operator configured
``HAIL_MAIL_BASE_DOMAIN`` (the ``<org>`` part is derived from your
organization id; the ``<user>`` part comes from ``HAIL_MAIL_FROM``
/ ``HAIL_MAIL_DEFAULT_USER_PREFIX``, or an explicit row created
via ``POST /email-domains``). When supplied, ``from_`` must match
a verified row already in ``email_domains`` (register one with
the website console or ``POST /email-domains``).
``from_name`` is an optional display name rendered on the
From: header ("Acme Billing <billing@acme.com>"). Control
characters are rejected.
``metadata`` is free-form JSON attached to the email record.
``idempotency_key`` defaults to a fresh UUID and is returned
in the response under ``idempotency_key`` â pass the same
value on a retry to replay rather than re-send. A new key
is a new message.
``attachment_ids`` are ids returned by ``upload_email_attachment``
â upload a file first, then pass its id(s) here to attach it.
Example:
send_email(to=["alice@example.com"],
subject="Welcome",
recipient_consent=True,
body_text="Thanks for signing up.")
Returns the ``EmailResponse`` dict (id, status, from_address,
to_addresses, sent_at, provider_message_id, ...). On failure
returns ``{"error": "<message>"}`` instead.
Esquema de entrada
{'type': 'object', 'title': 'send_email_toolArguments', 'required': ['to', 'subject', 'recipient_consent'], 'properties': {'cc': {'anyOf': [{'type': 'array', 'items': {'type': 'string'}}, {'type': 'null'}], 'title': 'Cc', 'default': None}, 'to': {'type': 'array', 'items': {'type': 'string'}, 'title': 'To'}, 'bcc': {'anyOf': [{'type': 'array', 'items': {'type': 'string'}}, {'type': 'null'}], 'title': 'Bcc', 'default': None}, 'from_': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'From', 'default': None}, 'subject': {'type': 'string', 'title': 'Subject'}, 'metadata': {'anyOf': [{'type': 'object', 'additionalProperties': True}, {'type': 'null'}], 'title': 'Metadata', 'default': None}, 'reply_to': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Reply To', 'default': None}, 'body_html': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Body Html', 'default': None}, 'body_text': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Body Text', 'default': None}, 'from_name': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'From Name', 'default': None}, 'message_type': {'type': 'string', 'title': 'Message Type', 'default': 'informational'}, 'attachment_ids': {'anyOf': [{'type': 'array', 'items': {'type': 'string'}}, {'type': 'null'}], 'title': 'Attachment Ids', 'default': None}, 'consent_source': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Consent Source', 'default': None}, 'idempotency_key': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Idempotency Key', 'default': None}, 'recipient_consent': {'type': 'boolean', 'title': 'Recipient Consent'}, 'consent_obtained_at': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Consent Obtained At', 'default': None}}}
Esquema de salida
{'type': 'object', 'title': 'send_email_toolDictOutput', 'additionalProperties': True}
send_sms
Send an outbound SMS.
``to`` must be E.164 (e.g. ``+14155551234``). ``body`` is the
message text. With no ``from_``: UK (+44) and Germany (+49)
destinations use your organization's sender ID (or ``HAIL``, the
platform default); Australia (+61) always uses ``HAIL``; every
other destination uses your organization's oldest active
SMS-capable number and the API returns 422 when there is none.
SMS never uses the shared voice-call pool.
``recipient_consent`` is required: attest that you (the caller
triggering this request) have obtained the lawful consent needed
to text this recipient. The API rejects the request (422) if
this is not ``true`` â Hail does not verify consent for you. Set
``message_type="marketing"`` for promotional texts (this
additionally requires a non-empty ``consent_source``) â leave as
the default ``"informational"`` for transactional/service texts.
``idempotency_key`` defaults to a fresh UUID and is returned in
the response under ``idempotency_key`` â pass the same value on
a retry to replay rather than re-send.
Example:
send_sms(to="+14155551234", body="Your order shipped!",
recipient_consent=True)
Returns the ``SmsResponse`` dict (id, status, from_e164,
to_e164, segment_count, ...). On failure returns
``{"error": "<message>"}`` instead.
Esquema de entrada
{'type': 'object', 'title': 'send_sms_toolArguments', 'required': ['to', 'body', 'recipient_consent'], 'properties': {'to': {'type': 'string', 'title': 'To'}, 'body': {'type': 'string', 'title': 'Body'}, 'from_': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'From', 'default': None}, 'metadata': {'anyOf': [{'type': 'object', 'additionalProperties': True}, {'type': 'null'}], 'title': 'Metadata', 'default': None}, 'message_type': {'type': 'string', 'title': 'Message Type', 'default': 'informational'}, 'consent_source': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Consent Source', 'default': None}, 'idempotency_key': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Idempotency Key', 'default': None}, 'recipient_consent': {'type': 'boolean', 'title': 'Recipient Consent'}, 'consent_obtained_at': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Consent Obtained At', 'default': None}}}
Esquema de salida
{'type': 'object', 'title': 'send_sms_toolDictOutput', 'additionalProperties': True}
upload_email_attachment
Upload a file to attach to a future outbound email.
``content_base64`` is the file's raw bytes, base64-encoded.
Returns ``{"id": ..., "filename": ..., "content_type": ...,
"size_bytes": ...}`` â pass ``id`` in ``send_email``'s
``attachment_ids`` list. The id is reusable across many sends
and expires in 24h if never used. Files over 25MB (combined
with the message body and any other attachments, per send) are
rejected â host large files externally and link to them in the
body instead.
Esquema de entrada
{'type': 'object', 'title': 'upload_email_attachment_toolArguments', 'required': ['content_base64', 'filename', 'content_type'], 'properties': {'filename': {'type': 'string', 'title': 'Filename'}, 'content_type': {'type': 'string', 'title': 'Content Type'}, 'content_base64': {'type': 'string', 'title': 'Content Base64'}}}
Esquema de salida
{'type': 'object', 'title': 'upload_email_attachment_toolDictOutput', 'additionalProperties': True}
whoami
Identify the human whose credentials this session runs under.
Use it to sign or route mail as that person: pass their address as
``send_email(reply_to=...)`` so replies reach them rather than the
sending domain, which is often an unattended ``noreply@``.
Returns ``{"auth_kind", "organization_id", "user_id", "email",
"name"}``. ``user_id``/``email``/``name`` are null when the server
runs on a shared operator key (``auth_kind="shared"``) â there is no
human behind it, so send without a ``reply_to``.
Example:
whoami()
Esquema de entrada
{'type': 'object', 'title': 'whoami_toolArguments', 'properties': {}}
Esquema de salida
{'type': 'object', 'title': 'whoami_toolDictOutput', 'additionalProperties': True}
Historial
Cambios recientes en herramientas
Añadido
create_contact
29 de September de 2026 a las 02:41
Añadido
whoami
29 de September de 2026 a las 02:41
Añadido
list_email_domains
29 de September de 2026 a las 02:41
Añadido
lookup_contact
29 de September de 2026 a las 02:41
Añadido
list_contacts
29 de September de 2026 a las 02:41
Añadido
get_events
29 de September de 2026 a las 02:41
Añadido
get_email_stats
29 de September de 2026 a las 02:41
Añadido
get_email_events
29 de September de 2026 a las 02:41
Añadido
get_email_attachment
29 de September de 2026 a las 02:41
Añadido
get_email_raw
29 de September de 2026 a las 02:41
Añadido
list_emails
29 de September de 2026 a las 02:41
Añadido
get_email
29 de September de 2026 a las 02:41
Añadido
list_sms
29 de September de 2026 a las 02:41
Añadido
get_sms
29 de September de 2026 a las 02:41
Añadido
send_sms
29 de September de 2026 a las 02:41
Añadido
list_calls
29 de September de 2026 a las 02:41
Añadido
get_call
29 de September de 2026 a las 02:41
Añadido
upload_email_attachment
29 de September de 2026 a las 02:41
Añadido
send_email
29 de September de 2026 a las 02:41
Añadido
place_call
29 de September de 2026 a las 02:41
Descubrir
Servidores MCP similares
独行录 / opcmenu
io.github.yzlee/opcmenu
Supports founder and company discovery, collaboration goals and tasks, events and signups, networking, messaging, profiles, produ…
Odichat
io.github.odichat/mcp-odichat
Manages WhatsApp, Instagram, and Facebook inboxes with contacts, conversations, agents, automation rules, labels, canned response…
KaiCalls
com.kaicalls/kaicalls
Provides AI phone reception, outbound calling campaigns, call transcripts and recordings, lead management, routing, staff alerts,…
anima
io.github.anima-labs-ai/anima
Provides agent-owned email inboxes, phone and SMS identities, email drafting and sending, message search and threading, domains, …
agendaforge
app.agendaforge/agendaforge
Manages events, agendas, sessions, speakers, attendees, sponsors, forms, contacts, email templates, approvals, and organizer work…
Asyntai
com.asyntai/support-agent
Manages website AI support agents, their knowledge bases, conversations, live replies, leads, products, webhooks, analytics, and …
ikeytz – Schlüsseldienst Ludwigsburg
com.ikeytz/website
Publishes read-only business information, locksmith pricing and service details, and links for phone, email, and WhatsApp contact.
mailbox
bot.mailbox/mailbox
Manages physical inbound and outbound mail, postal fulfillment, OCR-backed mail context, facility messaging, delivery tracking, c…