addy-mcp

list_aliases

Read-only

List or search aliases with filters for activity, pinned status, labels, domains, recipients, and pagination to find and manage specific email aliases.

Instructions

List or search aliases. Results are paginated; the response includes meta with totals and page counts.

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_aliases"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number (1-based)
`sort`	No	Field to sort by
`active`	No	Only active (true) or inactive (false) aliases
`pinned`	No	Only pinned (true) or unpinned (false) aliases
`search`	No	Search alias email addresses and descriptions
`deleted`	No	'with' to include deleted aliases, 'only' for just deleted ones. Default excludes them.
`include`	No	Also return each alias's recipients or labels (the API allows only one per request)
`label_id`	No	Only aliases with this label id
`domain_id`	No	Only aliases on this custom domain id
`page_size`	No	Results per page (1-100)
`descending`	No	Sort descending
`username_id`	No	Only aliases on this username id
`recipient_id`	No	Only aliases forwarding to this recipient id

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Nov 12, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavior beyond that: results are paginated and the response carries a `meta` block with totals and page counts. It stops short of mentioning rate limits, permission/scope requirements, or any cap on deep pagination.

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?

Two short sentences, front-loaded with the verb and resource, and the pagination note follows logically. Nothing is wasted, though the total payload is thin for a tool with 13 parameters.

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

Completeness3/5

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

With 13 optional parameters, no output schema, and no sibling differentiation, the description covers only the basics plus pagination. It does helpfully describe the response envelope, which partially offsets the missing output schema, but it omits filter-combination semantics and when to prefer get_alias.

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%, with all 13 parameters individually documented in the schema, so the baseline of 3 applies. The description adds no extra meaning about how filters combine, how `search` interacts with `deleted`, or how `sort` and `descending` pair, so it neither compensates nor detracts.

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

Purpose4/5

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

"List or search aliases" gives a specific verb pair and a clear resource, so an agent immediately knows this is a read/query tool over aliases. It does not, however, distinguish itself from adjacent siblings such as get_alias or bulk_alias_action, leaving the boundary to be inferred from the name alone.

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

Usage Guidelines2/5

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

The description offers no when-to-use guidance, no exclusions, and no named alternative (e.g., when to use get_alias for a single alias instead). The only implied usage is that this retrieves a collection or performs a search, which an agent could infer from the name without the description.

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

Deploy Server