DomainKits

Domain Marketplace Search

market

Read-onlyIdempotent

Search currently registered domains that carry marketplace listing data, filtered by keyword, TLD, TLD type (generic or country-code), listing status, length, and character set. Results are live domains owned by someone.

Related: keyword_data, tld_check.

Input Schema

Name	Required	Description
`tld`	No	Filter by TLD, e.g. 'com', 'de', or a second-level suffix such as 'com.br'. A two-letter country code also covers its second-level suffixes. Provide WITHOUT keyword to enter TLD browse mode (requires a registered account)
`page`	No	Page number for pagination
`sort`	No	Sort order
`type`	No	Character set filter
`length`	No	Domain name length filter
`status`	No	Filter by status: 'forsale' for domains listed for sale
`exclude`	No	Negative keywords to exclude
`keyword`	No	Brand or industry term (min 2 chars). Substring matching applies at every length, including 2-character terms.
`position`	No	Keyword placement in domain name. Default is 'all' (substring match).
`tld_type`	No	Limit results to country-code TLDs ('cctld': suffixes ending in a two-letter code, including second-level ones such as 'com.br') or generic TLDs ('gtld': all other suffixes; internationalized country codes such as 'xn--p1ai' fall here). Omit to include both.
`no_hyphen`	No	Exclude hyphenated domains (true/false)
`no_number`	No	Exclude domains containing numbers (true/false)
`tld_count_max`	No	Maximum cross-TLD registration count for the name. Integer 0-10000. See tld_count_min.
`tld_count_min`	No	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.

Output Schema

Name	Required	Description
`data`	No
`page`	No
`total`	No	Number of results on this page
`success`	Yes
`max_page`	No
`total_found`	No	Total matching results across all pages

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026

addedInput schema / properties / tld_type

Added value: +{
+  "description": "Limit results to country-code TLDs ('cctld': suffixes ending in a two-letter code, including second-level ones such as 'com.br') or generic TLDs ('gtld': all other suffixes; internationalized country codes such as 'xn--p1ai' fall here). Omit to include both.",
+  "enum": [
+    "gtld",
+    "cctld"
+  ],
+  "type": "string"
+}

Changed1 schema field changedOct 13, 2026

changedInput schema / properties / tld / description

Previous value: -"Filter by TLD (e.g., 'com', 'net', 'org'). Provide WITHOUT keyword to enter TLD browse mode (gTLDs only; requires a registered account)"New value: +"Filter by TLD, e.g. 'com', 'de', or a second-level suffix such as 'com.br'. A two-letter country code also covers its second-level suffixes. Provide WITHOUT keyword to enter TLD browse mode (requires a registered account)"

Changed2 schema fields changedOct 3, 2026

removedOutput schema / properties / data / items / properties / components

Removed value: -{
-  "description": "Word segmentation of the domain prefix",
-  "type": "string"
-}

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."

Changed1 schema field changedSep 28, 2026

changedInput schema / properties / tld / description

Previous value: -"Filter by TLD (e.g., 'com', 'net', 'org'). Provide WITHOUT keyword to enter TLD browse mode (gTLDs only)"New value: +"Filter by TLD (e.g., 'com', 'net', 'org'). Provide WITHOUT keyword to enter TLD browse mode (gTLDs only; requires a registered account)"

Changed2 schema fields changedSep 3, 2026

changedInput schema / properties / keyword / description

Previous value: -"Brand or industry 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: +"Brand or industry 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)."

Changed2 schema fields changedAug 28, 2026

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"
+}

Changed3 schema fields changedAug 17, 2026

changedInput schema / properties / position / description

Previous value: -"Keyword placement in domain name. Default is 'start'. 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",
-  "contain"
-]New value: +[
+  "start",
+  "end",
+  "middle",
+  "all"
+]

addedInput schema / properties / status / enum
```
Added value: +[
+  "forsale"
+]
```

Changed2 schema fields changedAug 13, 2026

changedInput schema / properties / keyword / description

Previous value: -"Brand or industry term (min 2 chars)"New value: +"Brand or industry 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. Default is 'start'."New value: +"Keyword placement in domain name. Default is 'start'. Ignored when keyword is 2 characters (always start)."

AddedJul 27, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds the useful behavioral fact that results are live, owned domains (not parked or unregistered), but omits the account requirement for TLD browse mode (present only in the schema) and says nothing about result volume or pagination behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences plus a short related-tools pointer, front-loaded with the core scope statement and no filler. Every clause earns its place.

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?

With an output schema handling return values, 100% schema coverage on 14 params, and annotations covering the safety profile, the description provides enough to call the tool correctly. The remaining gap is sibling routing – nothing tells the agent why to choose market over market_price or available – which a 14-parameter tool in a crowded namespace would benefit from.

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% with 6 enums, so the schema already documents every parameter in detail (including browse mode and count ranges). The description merely names the filter categories (keyword, TLD, TLD type, listing status, length, character set) without adding syntax or format meaning beyond it, which is the baseline 3 case.

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?

Specific verb+resource: 'Search currently registered domains that carry marketplace listing data,' with the filter axes enumerated. 'Results are live domains owned by someone' implicitly separates it from the available/deleted/expired siblings, but it never names an alternative (e.g. market_price) or sharply delimits itself, so it stops short of full sibling differentiation.

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 'Related: keyword_data, tld_check' line is a routing hint but does not say when to prefer this tool over them, nor when not to use it versus market_price or available. Usage is only implied by the scope sentence about live registered domains, not stated as an explicit condition.

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

All DomainKits tools Inspect

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.

Domain Marketplace Search

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources