Skip to main content
Glama

Search newly registered domains

search_new_domains
Read-onlyIdempotent

Find domains registered in the last 1–7 days that contain or start with a query string for brand monitoring, typosquatting and phishing detection, and keyword trend tracking.

Instructions

Find domain names registered in the last 1-7 days that contain (or start with) a string: brand monitoring, typosquatting, phishing campaigns, keyword trends. Covers every TLD NetAPI updates daily (.com, .net, .org, .ru, .fr, .ch and 1,100+ more). Free with limits: up to 100 results per call without an account, more with a NetAPI plan. The complete daily lists of new domains are available to subscribers via get_download_url.

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": {
      "query": "<query>"
    },
    "name": "search_new_domains"
  }
}

Input Schema

NameRequiredDescriptionDefault
tldNoLimit to one TLD, e.g. "com"
daysNoHow many days back, 1-7 (default 1 = the latest daily list)
limitNoMaximum results (default 50; the cap depends on the access level)
matchNo"contains" (default) or "starts" (domain name starts with the query)
queryYesText to look for in the domain name (letters, digits, dots, hyphens; at least 4 characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds quota semantics ('up to 100 results per call without an account, more with a plan') plus coverage scope (~1,100+ TLDs updated daily). It does not describe result ordering or what a truncated result set looks like, so it stops short of a full 5.

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?

Three sentences, front-loaded with the core search behaviour, then coverage, then limits and the alternative. The first sentence is dense with comma-separated use cases, but every clause carries information and nothing is repeated from the schema verbatim.

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 read-only search tool with no output schema, the description supplies scope, coverage, quota, and an alternative tool, which is nearly everything an agent needs to call it correctly. Only result ordering and the shape of capped results are left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3; the description nonetheless adds meaning for `limit` by tying the result cap to access level, and confirms the `match` modes and the 1-7 day `days` window in prose. It does not add anything for `tld` or `query` beyond what the schema already states.

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 ('Find'), resource ('domain names registered in the last 1-7 days'), and the matching scope ('contain or start with a string'). It also names the sibling `get_download_url` as the source of full daily lists, so an agent can distinguish this tool from its neighbours without opening any schema.

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

Usage Guidelines5/5

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

Explicit when-to-use cases are given (brand monitoring, typosquatting, phishing campaigns, keyword trends) and an alternative path is named for the full-list case via `get_download_url`. The free-vs-subscriber boundary further tells the agent when this tool is sufficient versus when it is not.

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