Remove a customer-owned hostname from the project whitelist and return the removed domain record. Future pixel loads and redirects from that hostname are rejected.
| Name | Required | Description | Default |
|---|---|---|---|
| hostname | Yes | Hostname only, e.g. example.com, not a full URL. | |
| projectId | No | Optional project ID. Omit only when the API key is project-scoped or the account has a clear default project. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark the tool as destructive (destructiveHint=true). The description adds value by stating that the removed domain record is returned and that future pixel loads and redirects are rejected, providing context beyond the annotation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise at two sentences, with no extraneous words. The structure is logical: state the action and return value, then the consequence.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (2 params, no output schema) and the presence of annotations covering destructiveness, the description is fairly complete. It could mention irreversibility, but that is implied by destructiveHint.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema fully documents both parameters. The description does not add significant new meaning beyond what the parameter descriptions provide.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'remove', the resource 'customer-owned hostname from the project whitelist', and the consequence (future requests rejected). It effectively distinguishes from sibling tools like domains_add and domains_list.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implicitly indicates when to use (when removing a domain) but does not provide explicit guidance on when not to use or alternatives. The context from sibling tools provides differentiation, but no exclusions or prerequisites are stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource and action combination (e.g., domains_add, experiments_create, goals_deactivate, reports_experiment_chart). There is no overlap or ambiguity; even the three report tools serve clearly different purposes (totals, time-series, channel breakdown).
The vast majority of tools follow a resource_action snake_case pattern (domains_add, experiments_list). A couple deviate (billing_portal, usage_summary) but still place the resource first, making the pattern predictable and easy to parse.
With 23 tools covering projects, domains, experiments, goals, reports, billing, health, and usage, the count is well-scoped for a split-testing platform. Each tool addresses a specific need without ballooning into excessive granularity.
The tool surface provides CRUD-like operations for core entities (projects, experiments, goals, domains) and essential report types. Minor gaps exist (no goal update tool, no experiment delete—only archive) but these are reasonable trade-offs for the domain.
