Skip to main content
Glama

Active Domain Search

active
Read-onlyIdempotent

Search active registered domains from a database of more than 360 million names, filtered by keyword, TLD, length, and character set. Covers generic TLDs plus more than 100 country-code TLDs, including second-level registrations such as .com.br, .co.uk and .com.tw (tld 'br' returns the whole .br family, 'com.br' returns that suffix alone). Which country-code TLDs you can see depends on your plan; asking for one outside it returns a message saying so. A market-analysis instrument for keyword distribution and saturation; results are registered domains, not available for registration.

Related: expired, whois, dns.

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": "active"
  }
}

Input Schema

NameRequiredDescriptionDefault
tldNoFilter by TLD, e.g. 'com', 'ai', or a second-level suffix such as 'com.br'. A two-letter country code also covers its second-level registrations ('br' includes 'com.br'). When keyword is omitted, this is the browse target (TLD browse mode requires a registered account).
pageNoPage number for pagination
sortNoSort order
typeNoCharacter set filter
lengthNoDomain name length filter
statusNoFilter by status: 'forsale' for domains listed for sale
keywordNoBrand or industry term (min 2 chars). Omit to use TLD browse mode, which requires a registered account.
positionNoKeyword placement in domain name. Default is 'all' (substring match). Unlike the other search tools, this one has no minimum-length restriction on substring matching.
no_hyphenNoExclude hyphenated domains (true/false)
no_numberNoExclude domains containing numbers (true/false)
tld_count_maxNoMaximum cross-TLD registration count for the name. Integer 0-10000. See tld_count_min.
tld_count_minNoMinimum cross-TLD registration count for the name. Integer 0-10000. Combine with tld_count_max for a range; set both equal for an exact count.

Output Schema

NameRequiredDescriptionDefault
dataNo
pageNo
errorNoError message when success is false
totalNoNumber of results on this page
successNo
max_pageNo
total_foundNoTotal matching results across all pages; the primary metric for comparative analysis

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / required
      Removed value: -[
      -  "success"
      -]
  2. Changed1 schema field changed
    • changedInput schema / properties / tld / description
      Previous value: -"Filter by TLD (e.g., 'com', 'net', 'org'); when keyword is omitted, this is the browse target (TLD browse mode requires a registered account)"New value: +"Filter by TLD, e.g. 'com', 'ai', or a second-level suffix such as 'com.br'. A two-letter country code also covers its second-level registrations ('br' includes 'com.br'). When keyword is omitted, this is the browse target (TLD browse mode requires a registered account)."
  3. Changed1 schema field changed
    • changedOutput schema / properties / data / items / properties / marketplace / description
      Previous value: -"Sale platform code where the domain is listed: se=Sedo, go=GoDaddy, at=Atom, vn=Venture, pd=PerfectDomain, gn=Gname. Present only when the domain is listed for sale."New value: +"Sale platform code where the domain is listed: se=Sedo, go=GoDaddy, at=Atom, vn=Venture, pd=PerfectDomain, gn=Gname, hu=HugeDomains. Present only when the domain is listed for sale."
  4. Changed1 schema field changed
    • changedOutput schema / properties / total_found / description
      Previous value: -"Total matching results across all pages — primary metric for comparative analysis"New value: +"Total matching results across all pages; the primary metric for comparative analysis"
  5. Changed2 schema fields changed
    • changedInput schema / properties / keyword / description
      Previous value: -"Brand or industry term (min 2 chars). Omit to use TLD browse mode."New value: +"Brand or industry term (min 2 chars). Omit to use TLD browse mode, which requires a registered account."
    • changedInput schema / properties / tld / description
      Previous value: -"Filter by TLD (e.g., 'com', 'net', 'org'); when keyword is omitted, this is the browse target"New value: +"Filter by TLD (e.g., 'com', 'net', 'org'); when keyword is omitted, this is the browse target (TLD browse mode requires a registered account)"
  6. Changed2 schema fields changed
    • addedInput schema / properties / tld_count_max
      Added value: +{
      +  "description": "Maximum cross-TLD registration count for the name. Integer 0-10000. See tld_count_min.",
      +  "type": "string"
      +}
    • addedInput schema / properties / tld_count_min
      Added value: +{
      +  "description": "Minimum cross-TLD registration count for the name. Integer 0-10000. Combine with tld_count_max for a range; set both equal for an exact count.",
      +  "type": "string"
      +}
  7. Changed5 schema fields changed
    • changedInput schema / properties / length / enum
      Previous value: -[
      -  "<5",
      -  "5-10",
      -  "11-15",
      -  ">15"
      -]New value: +[
      +  "<5",
      +  "5-10",
      +  "11-15",
      +  "15+"
      +]
    • changedInput schema / properties / position / description
      Previous value: -"Keyword placement in domain name. Default is 'start' (prefix match) — pass position=contain explicitly for substring matching. Unlike the other search tools, this one has no minimum-length restriction on substring matching."New value: +"Keyword placement in domain name. Default is 'all' (substring match). Unlike the other search tools, this one has no minimum-length restriction on substring matching."
    • changedInput schema / properties / position / enum
      Previous value: -[
      -  "start",
      -  "end",
      -  "middle",
      -  "contain"
      -]New value: +[
      +  "start",
      +  "end",
      +  "middle",
      +  "all"
      +]
    • changedInput schema / properties / status / description
      Previous value: -"Filter by status — 'forsale' for domains listed for sale"New value: +"Filter by status: 'forsale' for domains listed for sale"
    • addedInput schema / properties / status / enum
      Added value: +[
      +  "forsale"
      +]
  8. Changed1 schema field changed
    • changedInput schema / properties / position / description
      Previous value: -"Keyword placement in domain name. Default is 'contain' (substring match)."New value: +"Keyword placement in domain name. Default is 'start' (prefix match) — pass position=contain explicitly for substring matching. Unlike the other search tools, this one has no minimum-length restriction on substring matching."
  9. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations cover the read-only/idempotent safety profile, and the description adds substantial context beyond them: plan-gated ccTLD access with a specific failure mode ('returns a message saying so'), TLD browse mode requiring a registered account, and the fact that this tool has no minimum-length restriction on substring matching unlike its peers.

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-loaded with the core purpose, then scope, then plan caveat, then the analytic framing, then a terse 'Related:' line. Dense but every sentence carries information; the .com.br/.co.uk/.com.tw enumeration is slightly redundant with the schema but aids scanning.

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 12-parameter, zero-required tool with an output schema, the description covers mode selection, plan gating, and result semantics well. The one gap is the default behavior when no parameters at all are supplied, which an agent could hit given zero required params.

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 all 12 parameters are already documented, and the tld hierarchy example ('br' returns the whole .br family) is repeated verbatim from the schema. The description only adds the browse-mode/account nuance for tld and keyword, so the baseline 3 applies.

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 and resource ('Search active registered domains') plus the backing corpus ('more than 360 million names') and the filter dimensions. It explicitly distinguishes itself from registration-availability siblings by saying 'results are registered domains, not available for registration' and names expired, whois, dns as related.

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?

Frames the tool as 'a market-analysis instrument for keyword distribution and saturation' and rules out the availability-check use case, which implicitly routes to `available`. It also flags that ccTLD visibility depends on plan. It stops short of explicit 'use X instead when Y' routing for the remaining siblings, so not a 5.

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.