Skip to main content
Glama

mcp-livedatapro

by site.livedatapro
OverviewDiscussionsAdmin

searchExpiredDomains

Find recently dropped, expired, or deleting domains with high backlink authority available for immediate registration. Use when searching for recently dropped, expiring, or auctioned domains with existing SEO backlink authority available for registration. Do not use for checking WHOIS records of a specific known domain (use getDomainWhois). Returns up to 50 available domains filtered by keyword and TLD with Domain Authority scores.

Input Schema

NameRequiredDescriptionDefault
tldNoTop-level domain extension filter without leading dot (defaults to 'com').com
keywordNoKeyword substring to match in dropped/expiring domain names (defaults to 'ai').ai

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / keyword / default
      Added value: +"ai"
    • addedInput schema / properties / keyword / examples
      Added value: +[
+  "agent"
+]
    • addedInput schema / properties / keyword / minLength
      Added value: +2
    • addedInput schema / properties / tld / default
      Added value: +"com"
    • addedInput schema / properties / tld / enum
      Added value: +[
+  "com",
+  "io",
+  "ai",
+  "org",
+  "net",
+  "site",
+  "co",
+  "dev"
+]
    • addedInput schema / properties / tld / examples
      Added value: +[
+  "ai"
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / keyword / description
      Previous value: -"Filter domain names containing specific keyword (e.g., ai, crypto, finance)"New value: +"Keyword substring to match in dropped/expiring domain names (defaults to 'ai')."
    • changedInput schema / properties / tld / description
      Previous value: -"Top-level domain filter (e.g., com, io, ai, org)"New value: +"Top-level domain extension filter without leading dot (defaults to 'com')."
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and mostly succeeds: it discloses the 50-result cap, that only currently registrable domains are returned, that results carry Domain Authority scores, and the filtering dimensions. It omits freshness/lag of drop data, cost/auth requirements, and pagination beyond the cap, which keeps it below a 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?

Front-loaded and well ordered (what it does, when to use, when not to, what it returns). However, the second sentence largely re-enumerates the domain states from the first sentence ('dropped, expired, deleting' vs 'dropped, expiring, auctioned'), which is redundant and also introduces 'auctioned', a state that sits awkwardly with 'available for immediate registration'.

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 two-parameter search tool with no output schema, the description does the needed work: it explains the returned set and its size cap and scoring field. It stops short of noting data freshness, result ordering, or pricing, which an agent selecting among data-lookup siblings could reasonably want.

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 coverage is 100% — both 'tld' (with enum and default 'com') and 'keyword' (minLength, default 'ai') are fully documented in the schema. The description only restates that filtering is by keyword and TLD, adding no syntax, matching-behavior, or wildcard guidance beyond what the schema already says.

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') plus a precisely scoped resource: recently dropped/expired/deleting domains with backlink authority that are available to register. It explicitly names the sibling it is not (getDomainWhois), so an agent can separate the two without reading either 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?

Gives an explicit 'Use when...' trigger and a 'Do not use for... (use getDomainWhois)' exclusion with the correct alternative named. The routing decision is fully determined by the text.

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

All mcp-livedatapro toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources