Skip to main content
Glama

Delete a tracking domain

delete_tracking_domain
DestructiveIdempotent

Use this when the user no longer wants their campaign links to go through their tracking domain, or to replace it with another hostname. New emails then use the shared link address. Links already sent work only while the hostname's CNAME record stays in place, so tell the user to keep the record. A domain that was ever active stays held by the organization, and adding its hostname again brings it back; one never active is deleted and its hostname is free. Refused for a minute or two while the domain is being switched off. Free.

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": {
      "trackingDomainId": "<trackingDomainId>"
    },
    "name": "delete_tracking_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
trackingDomainIdYesThe tracking domain's id.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the destructiveHint/idempotentHint/openWorldHint annotations, it explains what is and isn't destroyed: already-sent links keep working only while the CNAME remains, an ever-active domain stays held by the organization and can be restored by re-adding the hostname, while a never-active domain is truly deleted and its hostname freed. It also discloses the temporary refusal window and that the action is free.

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?

It is front-loaded with the usage trigger, then proceeds through consequences, lifecycle caveats, and the refusal/free notes, with no filler sentences. Some sentences are dense and pack multiple facts, but each carries information an agent would otherwise have to guess.

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 destructive, single-parameter tool with no output schema, the definition covers trigger conditions, link-continuity effects, reversibility semantics, the transient refusal state, and cost. An agent has everything needed to call it and to advise the user about the CNAME record.

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 100% for the single trackingDomainId parameter, so the schema already carries its meaning. The description adds nothing about the id's expected format or how to obtain it, so the baseline 3 applies.

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?

The description states the concrete outcome: campaign links stop routing through the tracking domain and new emails fall back to the shared link address, plus the replace-with-another-hostname case. It is specific about the resource and effect, though the verb 'delete' itself is only implied by the name/title rather than stated in the text.

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?

It gives clear triggering conditions (user no longer wants links through the domain, or wants to swap hostnames) and a precondition ('Refused for a minute or two while the domain is being switched off'), which doubles as a when-not. It stops short of naming a specific sibling to use for replacement, leaving the agent to infer create_tracking_domain.

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