Skip to main content
Glama

continental.net Expiring Domains

Search expiring domains

search_expiring_domains
Read-only

Search expiring and deleted domains with backlinks. Returns domain, DR (Ahrefs), DA, TF, CF, TF/CF, referring domains, first year, Clean Score (0-100, Wayback history), state (backorder / free / caught / watch), drop date and a page URL. Lists: all, today, tomorrow, available (deleted and free to register now), high-dr (DR 20+), clean-domains, aged-domains, short-domains, brandable-domains, domains-with-history.

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

Input Schema

NameRequiredDescriptionDefault
tldNoExtension without dot, e.g. "com"
listNoall
sortNodr
limitNo
min_drNo
keywordNoPart of the domain name, e.g. "travel"
no_digitsNo
max_lengthNoMax characters before the extension
no_hyphensNo
clean_linksNoOnly TF/CF 0.5 or more
min_ref_domainsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine payload context beyond that — the field set returned, the 0-100 Clean Score definition tied to Wayback history, and the possible state values — but says nothing about pagination, result caps, rate limits, or query cost.

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 is front-loaded in the opening clause, and there are only two sentences with no filler. The second sentence is a dense run-on enumeration of eleven return fields, which is defensible given there is no output schema but makes it harder to scan.

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

Completeness3/5

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

Without an output schema, the return-field list is genuinely needed and present. For an 11-parameter search tool with no annotations covering paging, the missing pieces are meaningful: whether results are paginated, what limit=50 actually caps, how sort interacts with list, and what an empty result means.

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 only 36% across 11 parameters, so the description carries real burden; it partially compensates by defining the list values ('high-dr' = DR 20+, 'available' = deleted and free now) and the state field. It leaves the seven sort modes, tld matching behavior, min_ref_domains, and no_digits/no_hyphens entirely to the schema, and never explains how filters interact with a chosen list.

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 first sentence states a specific verb and resource ('Search expiring and deleted domains with backlinks'), and the rest lists exactly which fields come back. It does not, however, position itself against the sibling tools drop_stats or get_domain, so an agent must infer the boundary from names alone.

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?

The enumeration of list modes ('all, today, tomorrow, available...') hints at use cases, and 'available (deleted and free to register now)' clarifies one mode. But there is no explicit when-to-use guidance, no statement of when to prefer get_domain for a single domain or drop_stats for aggregate trends, and no guidance on combining filters.

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.

Resources