DomainKits

Domain Marketplace Search

market

Read-onlyIdempotent

Search currently registered domains that carry marketplace listing data, filtered by keyword, TLD, listing status, length, and character set. Results are live domains owned by someone.

Related: keyword_data, tld_check.

Input Schema

TableJSON Schema

Name	Required	Description
`tld`	No	Filter by TLD (e.g., 'com', 'net', 'org'). Provide WITHOUT keyword to enter TLD browse mode (gTLDs only; 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).
`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

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

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.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the important behavioral fact that results are live, owned domains – but omits pagination/result-volume behavior and the TLD-browse account requirement, which only appears in the schema.

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?

Two tight sentences: purpose and scope first, siblings second. No filler. Could be marginally tighter but is well front-loaded.

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 present and 100% schema coverage, the description needn't explain returns or parameters; it correctly focuses on scope and sibling routing. It stops just short of full completeness by omitting the TLD-browse account requirement and pagination behavior.

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 fully documents all 13 parameters; the description only paraphrases the filter axes. Baseline 3 is appropriate since the description adds no syntax, defaults, or interaction rules beyond the schema.

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+resource ('Search currently registered domains that carry marketplace listing data') and enumerates the filter axes, plus adds a crucial scoping fact ('Results are live domains owned by someone') that distinguishes it from registration-availability siblings. The 'Related:' line explicitly routes to keyword_data and tld_check.

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

Usage Guidelines4/5

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

Names two related alternatives (keyword_data, tld_check), giving the agent a routing signal. However, it does not state when to use market vs. market_price, available, or expired, all of which are adjacent sibling tools in the same list.

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