eurodns-mcp

Add or remove a mailbox alias

eurodns_email_set_alias

Destructive

Add or remove an email alias for a subscription. Manage specific addresses for a mailbox by specifying the alias and action.

Instructions

Adds (action: add) or removes (action: remove) the address in alias, which delivers into the mailbox of the email subscription id, and returns the updated subscription. Use it for one named extra address; to accept every unknown address at the domain use eurodns_email_set_catchall instead. Removing an alias bounces mail sent to it from then on. The subscription id comes from eurodns_subscription_get for product email.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Numeric id of the email subscription, from eurodns_subscription_get with product email and no id.
`alias`	Yes	The alias address for the mailbox, e.g. sales@example.com.
`action`	Yes	add creates the alias; remove deletes it.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes	Response body as returned by the API.
`status`	Yes	Upstream HTTP status code.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.11.0Sep 8, 2026

changedInput schema / properties / id / description

Previous value: -"Numeric id of the email subscription, from the list eurodns_email_get_subscription returns when called without an id."New value: +"Numeric id of the email subscription, from eurodns_subscription_get with product email and no id."

Addedv0.10.0Sep 7, 2026

TDQS

A5/5.0

Behavior5/5

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

Although the annotations already indicate destructive and non-idempotent behavior, the description adds specific context that removing an alias causes mail sent to it to bounce. This extra detail helps the agent understand the real-world consequence of the action.

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

Conciseness5/5

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

The description is concise and well-structured—two sentences cover the core action, return value, usage context, and alternative. Parameter descriptions are compact and informative without unnecessary detail.

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 the full input schema, output schema presence, and sibling context, the description provides all necessary information for an agent to call the tool correctly. No critical details are missing.

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

Parameters5/5

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

All three parameters are documented with meaningful descriptions: id explains its origin from subscription_get, alias includes an example format, and action explicitly maps 'add' and 'remove' to create/delete behavior. The schema coverage is complete.

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 clearly states the tool adds or removes an alias address for a mailbox and returns the updated subscription. It also explicitly differentiates from the catchall sibling by noting its use case for one named extra address.

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

Usage Guidelines5/5

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

The description explicitly states when to use this tool (for one named extra address) and when to use the alternative (eurodns_email_set_catchall for every unknown address). This gives the agent clear selection guidance.

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

Deploy Server