Skip to main content
Glama

Expiring Domains Search

expired
Read-onlyIdempotent

Search domains in the deletion cycle: expired, in redemption, or pending delete. Still held by the current registrant, with time-sensitive acquisition windows. Filter by lifecycle status, TLD, age range, length, character set, and registrar.

Note: registrars may renew a domain after it expires, and expiry information here is gathered through multiple channels, so some domain statuses may not match live WHOIS.

Related: monitor, deleted, whois.

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

Input Schema

NameRequiredDescriptionDefault
tldNoFilter by TLD (e.g., 'com', 'net', 'org')
pageNoPage number for pagination
sortNoSort order
typeNoCharacter set filter
lengthNoDomain name length filter
statusNoexpired = in registrar auction, redemption = owner can reclaim, pending_delete = drops in 1-5 days
excludeNoNegative keywords to exclude
keywordNoSearch term (min 2 chars). Substring matching applies at every length, including 2-character terms.
positionNoKeyword placement in domain name. Default is 'all' (substring match).
age_rangeNoHistorical age of the domain
no_hyphenNoExclude hyphenated domains
no_numberNoExclude domains containing numbers
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. Matches the prefix_tld_count field in results.
registrar_nameNoRegistrar name or part of it, case-insensitive, one value (e.g. 'namecheap' matches 'NameCheap Inc.').

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / required
      Removed value: -[
      -  "success"
      -]
  2. Changed3 schema fields changed
    • removedInput schema / properties / hold
      Removed value: -{
      -  "description": "Registry hold status",
      -  "enum": [
      -    "no_hold",
      -    "has_hold"
      -  ],
      -  "type": "string"
      -}
    • addedInput schema / properties / registrar_name
      Added value: +{
      +  "description": "Registrar name or part of it, case-insensitive, one value (e.g. 'namecheap' matches 'NameCheap Inc.').",
      +  "type": "string"
      +}
    • addedOutput schema / properties / data / items / properties / registrar_name
      Added value: +{
      +  "description": "Registrar of the domain, empty when unknown. Present on plans that include the registrar_name filter.",
      +  "type": "string"
      +}
  3. Changed2 schema fields changed
    • changedInput schema / properties / keyword / description
      Previous value: -"Search term (min 2 chars). IMPORTANT: 2-character keywords match the START of the name only; 'contain' and 'end' are unavailable at this length and total_found will exclude mid-name matches. Use 3+ characters for true substring matching."New value: +"Search term (min 2 chars). Substring matching applies at every length, including 2-character terms."
    • changedInput schema / properties / position / description
      Previous value: -"Keyword placement in domain name. Default is 'all' (substring match). Ignored when keyword is 2 characters (always start)."New value: +"Keyword placement in domain name. Default is 'all' (substring match)."
  4. 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. Matches the prefix_tld_count field in results.",
      +  "type": "string"
      +}
  5. Changed2 schema fields changed
    • changedInput schema / properties / position / description
      Previous value: -"Keyword placement in domain name. Default is 'contain'. Ignored when keyword is 2 characters (always start)."New value: +"Keyword placement in domain name. Default is 'all' (substring match). Ignored when keyword is 2 characters (always start)."
    • changedInput schema / properties / position / enum
      Previous value: -[
      -  "start",
      -  "end",
      -  "middle",
      -  "contain"
      -]New value: +[
      +  "start",
      +  "end",
      +  "middle",
      +  "all"
      +]
  6. Changed2 schema fields changed
    • changedInput schema / properties / keyword / description
      Previous value: -"Search term (min 2 chars)"New value: +"Search term (min 2 chars). IMPORTANT: 2-character keywords match the START of the name only; 'contain' and 'end' are unavailable at this length and total_found will exclude mid-name matches. Use 3+ characters for true substring matching."
    • changedInput schema / properties / position / description
      Previous value: -"Keyword placement in domain name"New value: +"Keyword placement in domain name. Default is 'contain'. Ignored when keyword is 2 characters (always start)."
  7. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and non-open-world, so the safety profile is covered. The description adds genuinely new behavioral context: registrars may renew after expiry and statuses are aggregated from multiple channels, so results may diverge from live WHOIS — a data-reliability caveat an agent needs before acting on results.

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?

Purpose and scope are front-loaded in the first sentence, the caveat note is compact and high-value, and nothing is padded. The 'Related:' line is the only weak element — a bare name list that consumes space without conveying differentiation.

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 15-parameter, all-optional search tool with a full output schema and complete annotations, the description covers purpose, scope, filter surface, and data-trust caveats. Pagination behavior and result-field semantics are only in the schema, which is acceptable given the output schema exists, but leaves a small 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 description coverage is 100% and the enums are self-documenting (status even explains the three lifecycle states), so the schema carries the semantic load. The description's filter list ('lifecycle status, TLD, age range, length, character set, and registrar') merely restates a subset of the parameters without adding format or interaction detail, so baseline 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 names a specific verb and resource ('Search domains in the deletion cycle') and scopes it precisely to three lifecycle states, adding the key qualifier 'Still held by the current registrant,' which implicitly separates it from a deleted/available-domain tool. It stops short of explicitly contrasting behavior with named siblings, keeping it below a 5.

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

Usage Guidelines3/5

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

It conveys the context in which the tool applies (time-sensitive acquisition windows within the deletion cycle) but gives no explicit when-to-use/when-not guidance. The trailing 'Related: monitor, deleted, whois' names alternatives without stating the condition that selects each one, leaving the routing decision to inference.

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.