list_mailboxesList all your email addresses. Optionally filter by domain. API: GET /api/emails (or GET /api/email).
| Name | Required | Description | Default |
|---|---|---|---|
| domain | No | Filter by domain, e.g. mysite.com. Omit to list all |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. The verb 'List' indicates a read operation, and 'your email addresses' suggests it's scoped to the authenticated user. However, the description does not explicitly disclose safety, permissions, or any limitations beyond the domain filter. The API endpoint note is interesting but does not add behavioral depth.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise and front-loaded: 'List all your email addresses' immediately states the core purpose. The optional filter and API endpoint note are additional but compact. No fluff or repetition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple list tool with one optional parameter and no output schema, the description covers the essential purpose and filtering. It could mention that only email addresses are returned or address pagination, but the current level is sufficient for a task with limited complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% coverage with a clear description for the `domain` parameter. The tool description merely restates 'Optionally filter by domain' without adding new meaning. Since schema description coverage is high, baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'List all your email addresses' – a specific verb and resource. It also mentions the optional domain filter, which distinguishes it from other list tools. The name and description align perfectly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use this tool (to list email addresses) and provides a filter option, but it does not explicitly state exclusions or alternatives. For example, it does not clarify that this lists mailboxes, not aliases, which could be confused with sibling tools like list_mailbox_aliases.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
While most tools have distinct purposes, several clusters overlap significantly (e.g., check_email, check_email_deliverability, get_email_deliverability, get_domain_email_status; buy_domain, buy_aftermarket, acquire_domain). The descriptions are detailed and help differentiate, but the sheer number of tools makes it challenging for an agent to select the correct one without careful reading.
The dominant pattern is verb_noun with underscores (e.g., create_mailbox, list_domains), but there are notable inconsistencies: destructive actions mix delete/remove/cancel/revoke/unsell, and a few names deviate entirely (search, dns_check, domain_status). The pattern is recognizable but not uniformly applied.
With 122 tools, this vastly exceeds the 50+ threshold for extreme mismatch. Even for a comprehensive domain and email platform, the tool count is overwhelming and will likely hinder agent performance through excessive choice and context bloat.
The server covers a wide range of domains, DNS, email, marketplace, negotiations, transfers, webhooks, tokens, and billing. Minor gaps exist, such as no update operation for mail rules, no direct domain deletion, and limited mailbox configuration beyond forwarding and credentials, but most lifecycle workflows are supported.