Skip to main content
Glama

Remove sending domain

domain_remove
DestructiveIdempotent

Removes the sending domain from this workspace. Destructive: campaigns cannot be scheduled from it afterwards, and adding it back gives new DNS records to set up again. Refused with domain_in_use while a campaign is scheduled on it. Uses no quota. Only call when the person explicitly asked to remove this exact domain. Requires API key scope: account.

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": "<domain>",
      "confirm": "<confirm>"
    },
    "name": "domain_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesA sending domain or subdomain, for example mail.example.com. No https://, no path.
confirmYesMust be true, and only after the person explicitly asked to remove this domain.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well past the annotations by disclosing what the destruction costs (campaigns can no longer be scheduled, DNS records must be re-set up on re-add), the exact error code and trigger for refusal, quota impact ("Uses no quota"), and the required API key scope. That is precisely the behavior an agent cannot get from destructiveHint=true alone.

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?

Five short sentences, front-loaded with the destructive consequence, then the error condition, quota, and the invocation gate. No filler; each sentence carries a distinct fact an agent needs.

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?

For a two-parameter destructive tool with no output schema, the description covers irreversibility, the refusal path, the authorization scope, and the human-consent requirement. Nothing an agent needs in order to decide whether and how to call it 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%, so both domain format and the confirm const:true gate are fully documented in the schema; the baseline of 3 applies. The description reinforces the confirm gate with the "only when explicitly asked" framing but adds no new syntax or format detail beyond the schema.

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?

States a specific verb and resource ("Removes the sending domain from this workspace") with explicit scope ("this workspace"). It also implicitly distinguishes itself from the add counterpart by noting that re-adding yields new DNS records, so an agent can identify the operation without opening the schema.

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

Usage Guidelines4/5

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

Gives a clear gating condition ("Only call when the person explicitly asked to remove this exact domain") and a documented refusal precondition ("domain_in_use while a campaign is scheduled"). What is missing is an explicit pointer to the prerequisite sibling, e.g. that the campaign must be cancelled first, leaving the agent to infer it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources