Skip to main content
Glama

Add a tracking domain

create_tracking_domain

Use this when the user wants their own subdomain, instead of a shared one, in the tracked links of their campaign emails. Adds the hostname as the organization's tracking domain, with its dnsTarget: the user must then add one CNAME record at their DNS provider, named after the hostname and pointing to dnsTarget. It becomes active once the record is found and its certificate is issued, usually within half an hour; it is checked every 5 minutes for about a day. It takes a subdomain of at least three labels, such as go.example.com. An organization has one tracking domain at a time, and a hostname another organization holds is refused. Campaigns with click tracking on use it; the open tracking image and the unsubscribe link do not. 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": {
      "hostname": "<hostname>"
    },
    "name": "create_tracking_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostnameYesA subdomain of a domain you own, such as `go.fernway.co`, without `https://` or a path: the hostname the tracked links of your campaign emails will go through. It needs at least three labels, so `fernway.co` is refused. It is lower-cased.

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?

Goes well beyond the annotations by disclosing the async activation flow: one CNAME record at the user's DNS provider pointing at dnsTarget, activation after record detection and certificate issuance, roughly 30-minute typical latency, and 5-minute polling for about a day. It also clarifies scope (campaign click tracking uses it; open-tracking image and unsubscribe link do not) and cost (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?

Front-loads the trigger condition, then the action, then the DNS mechanics and constraints. Dense but readable; the three-label rule is repeated from the schema, which is mild waste but not damaging.

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?

With no output schema, the description still explains that a dnsTarget is returned and what the user must do with it, plus the activation timeline and the one-per-organization and cross-organization constraints. An agent has enough to call this and set expectations correctly.

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 the hostname format, label minimum, lower-casing, and no-scheme rule are already documented in the schema. The description restates the three-label requirement and gives an example but adds no new parameter semantics beyond what is structured.

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 (adds) and resource (tracking domain) with the exact object it accepts (hostname) plus the returned dnsTarget. It does not explicitly name sibling operations such as verify_tracking_domain or delete_tracking_domain, but the lifecycle it describes makes the distinction inferable.

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?

Opens with an explicit trigger condition: use when the user wants their own subdomain instead of a shared one. It also gives preconditions (one tracking domain per organization, hostnames held by another organization refused), though it never says when to call verify or delete instead.

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