Skip to main content
Glama

PendingDelete.net

Search pending delete and dropped domains

search_domains
Read-onlyIdempotent

Search the domain names PendingDelete.net follows: in pending delete (the default) — the last five days before a registry deletes a name and anyone can register it — or, with status, the names released in the last 90 days: available (nobody has registered them again: anyone can register them now), caught (registered again since), or released (still being checked). The same filters as the site's advanced search: a keyword (contains, starts with, ends with, exact, doesn't contain) or a regular expression, words to leave out, a letter pattern, length, hyphens, numbers, IDN, extensions, adjoining .com/.net/.org registered, the drop or release date, confirmed drop times only, registrar, the year first registered, Linking Domains, Rank, real words, people's names and syllables. Each name comes with its drop (or release) date and time (US Eastern), length, registrar, registration date, Linking Domains and Rank (Common Crawl's web graph — not Moz DA or Ahrefs DR), which of the same name's .com, .net and .org are registered, and its page on PendingDelete.net. One answer holds 100 names unless limit says otherwise (up to 100), and the total; page gives the next ones, and each answer links the whole list on the site with its CSV. get_domain looks up one name in any status.

Input Schema

NameRequiredDescriptionDefault
idnNoInclude internationalised names (xn--). Default true.
pageNoWhich page of the results, from 1. Pages reach the first 10,000 names.
sortNoOrder of the names. Default drop_date: the nearest drop first (for the released statuses, the newest release first).drop_date
limitNoNames in this answer, 1–100 (more than 100 gives 100). Default 100.
matchNoHow keyword matches the name before the dot. Default contains.contains
orderNoasc or desc, as the words say (desc: the most Linking Domains, the highest Rank, the newest registration first). Default: nearest drop, A to Z, shortest, most Linking Domains, highest Rank, oldest registration, most adjoining registered.
regexNoA regular expression over the name before the dot, used instead of keyword (MySQL REGEXP; letters, digits, - ^ $ . * + ? ( ) [ ] { } | \ and commas; no back-references). E.g. ^[a-z]{4}$ for four letters.
statusNoWhich names: pending_delete (the default: they drop within five days), available (released in the last 90 days and not registered again: anyone can register them now), caught (released in the last 90 days and registered again since), or released (released, still being checked). One at a time.pending_delete
excludeNoLeave out names containing any of these (up to 5), e.g. ["shop", "247"].
hyphensNoInclude names with hyphens. Default true.
keywordNoText to find in the name before the dot: letters, digits and hyphens, e.g. "shop". How it matches is set by match.
numbersNoInclude names with digits. Default true.
min_rankNoA Rank of at least this (0–10 score of where the name stands in Common Crawl's web graph; see the answers for exactly how it is worked out).
surnamesNoOnly last names: alone, after a first name, or first with a trade's words after it (smithlaw).
syllablesNoExactly this many syllables (real words only).
extensionsNoExtensions to search, without the dot, e.g. ["com"] or ["com", "net", "org"]. Leave out for every extension PendingDelete.net tracks; most people want ["com"].
max_lengthNoMost characters before the dot (25 means 25 or more).
mens_namesNoOnly names starting with a man's first name (alone, or with a last name and more after it).
min_lengthNoFewest characters before the dot.
real_wordsNoOnly names made of everyday English words — not people's names or places.
registrarsNoThe registrar the name was with, as the registry writes it (up to 10); the commonest in pending delete now: GoDaddy.com, LLC; NameCheap, Inc.; GMO Internet Group, Inc. d/b/a Onamae.com; Spaceship, Inc.; Gname.com Pte. Ltd.; Dynadot Inc.
drop_date_toNoDrops or was released on or before this day: YYYY-MM-DD, or yesterday, today or tomorrow (US Eastern). The same day in both for one day.
womens_namesNoOnly names starting with a woman's first name.
drop_date_fromNoDrops (pending delete) or was released (the other statuses) on or after this day: YYYY-MM-DD, or yesterday, today or tomorrow (US Eastern).
letter_patternNoThe shape of the name before the dot: C a consonant, V a vowel, L any letter, N a digit; lowercase letters, digits and hyphens stand for themselves. E.g. CVCV (like "bobo"), LLLN, go-L.
registered_to_yearNoFirst registered in this year or earlier, e.g. 2005 for names older than about twenty years.
min_linking_domainsNoAt least this many other domains linking to the name in Common Crawl's web graph (the site's steps: 1, 10, 100, 1000).
adjoining_registeredNoAdjoining TLDs registered: keep names whose same name is registered right now in each of these, e.g. extensions ["com"] with ["net", "org"] gives the .com names whose .net and .org are both registered (someone owns them: a sign the name is wanted). From the zone files, once a day; .com, .net and .org names only.
registered_from_yearNoFirst registered in this year or later.
confirmed_drop_times_onlyNoOnly names whose drop time is worked out from the registry's own record of when the name entered pending delete, not estimated.

Output Schema

NameRequiredDescriptionDefault
toYes
fromYes
moreYes
pageYes
sortYes
limitYes
namesYes
orderYes
totalYesNames that match; null when more than 10,000 and not counted
statusYes
search_urlYes
total_textYes
download_maxYes
download_urlYes
figures_fromYes
released_daysYesFor the released statuses: how many days back they reach

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / registrars / description
      Previous value: -"The registrar the name was with, as the registry writes it (up to 10); the commonest in pending delete now: GoDaddy.com, LLC; NameCheap, Inc.; GMO Internet Group, Inc. d/b/a Onamae.com; Gname.com Pte. Ltd.; Spaceship, Inc.; Dynadot Inc."New value: +"The registrar the name was with, as the registry writes it (up to 10); the commonest in pending delete now: GoDaddy.com, LLC; NameCheap, Inc.; GMO Internet Group, Inc. d/b/a Onamae.com; Spaceship, Inc.; Gname.com Pte. Ltd.; Dynadot Inc."
  2. Changed1 schema field changed
    • changedInput schema / properties / registrars / description
      Previous value: -"The registrar the name was with, as the registry writes it (up to 10); the commonest in pending delete now: GoDaddy.com, LLC; NameCheap, Inc.; GMO Internet Group, Inc. d/b/a Onamae.com; Spaceship, Inc.; Gname.com Pte. Ltd.; Dynadot Inc."New value: +"The registrar the name was with, as the registry writes it (up to 10); the commonest in pending delete now: GoDaddy.com, LLC; NameCheap, Inc.; GMO Internet Group, Inc. d/b/a Onamae.com; Gname.com Pte. Ltd.; Spaceship, Inc.; Dynadot Inc."
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive search. The description adds substantial behavioral context beyond those annotations: it explains what each status means, that results are capped at 100 per answer with a total and page cursor, that each answer links the full list with a CSV, and that dates are US Eastern. It also clarifies that Rank is Common Crawl's web graph, not Moz DA or Ahrefs DR.

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 description is front-loaded with the core purpose and status options, and every sentence carries information. However, it is a dense single paragraph that repeats some schema-level details about filters and return fields, making it longer than strictly necessary. It is efficient but not maximally concise.

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

Completeness5/5

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

Despite the tool's complexity (30 parameters), the description covers the essential context an agent needs: status semantics, default behavior, result size and pagination, output fields, and sibling-tool routing. An output schema exists, so the description does not need to explain return values, but the extra behavioral details make it fully complete.

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 the schema already documents all 30 parameters in detail. The description provides a high-level summary of filter categories and repeats the status semantics, but it does not add meaningfully more per-parameter guidance than the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

The description opens with a specific verb and resource: searching the domain names PendingDelete.net follows. It also distinguishes the tool from its sibling by ending with 'get_domain looks up one name in any status.' An agent can immediately tell what this tool does and how it differs from get_domain.

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?

The description explicitly defines the default status (pending_delete) and the meaning of each alternative status (available, caught, released). It also provides a clear routing rule at the end: use get_domain for a single name in any status. This is explicit when-to-use guidance with a named alternative.

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.