Skip to main content
Glama

List tracking domains

list_tracking_domains
Read-only

Use this to show the organization's tracking domain and its status, or when the user asks which hostname the links in their campaign emails go through and whether it is working yet. An organization has at most one. Its status is pending_dns while it waits for its DNS record or its certificate, verifying while the hostname is set up, then active; it is failed when it has not become active after about a day of checks. dnsTarget is where its CNAME record must point. activeOnly returns only an active domain. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_tracking_domains"
  }
}

Input Schema

NameRequiredDescriptionDefault
activeOnlyNoOnly an active tracking domain, the only kind campaigns use. False when left out, which also lists a domain that is not active yet or that failed.

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?

Annotations already declare readOnlyHint, non-destructive, and closed-world, so the safety profile is covered. The description goes well beyond that with cardinality ('An organization has at most one'), the full status lifecycle (pending_dns, verifying, active, failed, including the ~1 day threshold), and the meaning of dnsTarget — real domain context an agent could not infer from structured fields.

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?

The usage trigger is front-loaded and the status explanation is ordered by lifecycle, which is easy to follow. The single status sentence is long and packs four states plus a timing threshold, but each fact earns its place for an agent that must interpret the result.

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

Completeness4/5

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

For a one-parameter, annotated, no-output-schema tool this is nearly complete: cardinality, status values, and dnsTarget are all explained, so an agent can both decide to call it and interpret the result. It does not enumerate the full returned field set (e.g. hostname), which is the only remaining 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 100% and the schema description for activeOnly already covers its default and exclusion behavior in detail. The description's line 'activeOnly returns only an active domain' restates the schema rather than adding new semantics, so the baseline of 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 opens with a specific verb and resource ('show the organization's tracking domain and its status') and adds a user-facing framing ('which hostname the links in their campaign emails go through'). It is clearly a read/list operation, distinct in spirit from create/delete/verify siblings, though it never names an alternative tool explicitly.

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 a concrete trigger condition ('when the user asks which hostname the links ... go through and whether it is working yet') and explains what each status means, which is the main interpretive task. It stops short of stating when NOT to use it, e.g. that verify_tracking_domain is the tool for initiating a check rather than just observing status.

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