addy-mcp

update_domain

Idempotent

Update a custom domain's settings on addy.io by changing its display name, editing the description, or setting a regex that controls which on-the-fly aliases are auto-created.

Instructions

Update a custom domain's description, from name, or auto-create regex.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain_id": "<domain_id>"
    },
    "name": "update_domain"
  }
}

Input Schema

Name	Required	Description
`domain_id`	Yes	The id (UUID) of the item
`from_name`	No	Display name for replies/sends
`description`	No
`auto_create_regex`	No	Regex limiting which on-the-fly aliases may be auto-created

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Nov 12, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds only the list of editable fields; it does not say whether omitted fields are left untouched, whether passing null clears a value, or whether changes take effect immediately for mail routing — the behaviors that actually matter for a partial-update mutation.

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?

A single front-loaded sentence with no filler, which is appropriately sized. The 'from name' typo slightly undercuts precision against the actual parameter name from_name.

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

Completeness2/5

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

This is a mutation with no output schema, and the description says nothing about the required domain_id, the partial-update contract, error behavior for unknown IDs, or what is returned. For a write tool whose behavior an agent cannot verify from structured fields, that is a substantial gap.

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 coverage is 75%: domain_id, from_name and auto_create_regex are documented in the schema, and description is only labeled. The description merely restates those field names (with 'from_name' mistyped as 'from name'), adding no format, constraints, or null-handling semantics beyond the schema.

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?

States a specific verb (Update) and resource (a custom domain) and enumerates the three mutable attributes, so the agent knows exactly what is changed. It does not distinguish itself from sibling update_* tools, but those target different resources, so confusion risk is low.

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?

There is no when-to-use guidance, no mention of prerequisites such as domain ownership or admin rights, and no indication of when to prefer create_domain or get_domain instead. The agent must infer all of this from the name alone.

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

Deploy Server