Skip to main content
Glama
hail

hail

Official

List email domains

list_email_domains
Read-onlyIdempotent

List a workspace's sending identities and default sender address to choose a verified, send-enabled email sender.

Instructions

List the workspace's sending identities and default sender address.

    Returns ``items``, ``next_cursor`` and ``default_from``.
    Only identities with ``verification_status="verified"`` can send.
    For ``kind="custom"``, ``domain`` is a domain supporting any local part.
    For ``kind="hail_mail"``, it is already a complete email address.
    One verified custom domain takes priority over the Hail mail address.
    With several verified custom domains, ``default_from`` is null and email sending requires an explicit sender.
    A custom domain with ``sends_enabled`` false cannot send: it is skipped for picks and refuses an explicit ``from_``.
    Toggle it with PATCH ``/v1/email-domains/{id}`` (custom domains only).
    

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_email_domains"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many items one page holds. ``next_cursor`` in the response points to the next page. Omitted: the API returns 50.
cursorNoPagination cursor: the ``next_cursor`` from the previous page. Omitted: the first page.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.32.0
    • addedInput schema / properties / cursor / description
      Added value: +"Pagination cursor: the ``next_cursor`` from the previous page. Omitted: the first page."
    • changedInput schema / properties / limit / anyOf
      Previous value: -[
      -  {
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "maximum": 200,
      +    "minimum": 1,
      +    "type": "integer"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / limit / description
      Added value: +"How many items one page holds. ``next_cursor`` in the response points to the next page. Omitted: the API returns 50."
  2. First observedv0.29.0

TDQS

A4.2/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, and the description adds substantial non-obvious behavior on top: only verification_status="verified" identities can send, a single verified custom domain outranks the Hail mail address, and multiple verified custom domains leave default_from null so an explicit sender is required. It also flags that a domain with sends_enabled=false is skipped for picks and rejects an explicit from_, which is exactly the kind of side-effect context an agent cannot get from annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first sentence, and the following sentences carry real semantic content about result interpretation. It is slightly long and the closing line about toggling via PATCH /v1/email-domains/{id} describes a separate operation rather than this tool, which is minor noise for a read-only listing call.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a read-only, zero-required-parameter listing tool with a full output schema, the description is complete. It explains what the returned fields mean (kind semantics for custom vs hail_mail, default_from priority) and the send-gating rules, so nothing an agent needs to act on the response is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and both limit and cursor are fully documented in the schema (page size, default 50, cursor round-trip). The description adds nothing about parameter syntax or format beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: "List the workspace's sending identities and default sender address." That is a distinct scope that no sibling (get_email, list_emails, route_email_domain) covers, so an agent can select this tool without comparing schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the agent can infer it should call this to discover which identities may send and what default_from resolves to. There is no explicit when/when-not statement and no routing to a sibling. The gating rules (verified-only, sends_enabled) do function as decision context, but they describe how to interpret results rather than when to invoke the tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.