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)
`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). 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.
`position`	No	Keyword placement in domain name. Default is 'all' (substring match). Ignored when keyword is 2 characters (always start).
`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

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior. The description adds useful context beyond those annotations: results are live domains owned by someone, clarifying that this is not a search over unregistered or hypothetical names. It does not discuss pagination, rate limits, or data freshness, but the annotations lower the bar for safety-related disclosure.

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?

The description is two sentences with no redundancy. The main action and scope are front-loaded, the result nature is stated clearly, and the related-tools hint is kept minimal.

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 tool with 13 parameters, complete schema coverage, and an output schema, the description is sufficient for selection and initial invocation. It could be stronger by explicitly contrasting with available/expired tools, but the schema and annotations carry the operational detail effectively.

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?

The input schema already describes all 13 parameters with 100% coverage, so the baseline is 3. The description's mention of keyword, TLD, listing status, length, and character set broadly aligns with the schema but adds no additional semantic detail beyond what the schema already provides.

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 uses a specific verb ('Search'), names the exact resource ('currently registered domains that carry marketplace listing data'), and enumerates the main filter dimensions. It distinguishes itself from siblings like available/expired/deleted by emphasizing the results are live domains owned by someone.

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 description implies when to use the tool: when you want registered domains with marketplace listing data rather than available, expired, or deleted domains. However, it only says 'Related: keyword_data, tld_check' without explicitly stating when to prefer this tool over those alternatives or when not to use it.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0

Disambiguation3/5

Many domain-search tools (active, aged, expired, deleted, market, nrds, nrds_live) have overlapping boundaries that depend on subtle lifecycle or listing distinctions, and pairs like bulk_tld/tld_check and nrds/nrds_live are easy to confuse. The detailed descriptions and related-tool hints help, but an agent still faces several nearly interchangeable choices.

Naming Consistency4/5

All tool names follow a consistent lowercase_snake_case convention, with no mixing of camelCase or inconsistent verb styles. However, the names use a noun/adjective pattern rather than a clear verb_noun action pattern, and acronyms like nrds, epp_status, and tld_rank make some names less predictable.

Tool Count2/5

32 tools is heavy for a domain toolkit, and several tools are close variants of the same search or check operation, such as active/aged/expired/deleted/market and nrds/nrds_live. The broad domain scope justifies some breadth, but the set would be much more focused with consolidation.

Completeness4/5

The toolset covers the core domain lifecycle well: availability, registration states, WHOIS, DNS, pricing, TLD statistics, safety, backlinks, typosquatting, and monitoring. The main gaps are that strategy can store data but has no retrieval or deletion action, and market pricing is limited to Sedo only.

Domain Marketplace Search

Input Schema

Output Schema

TDQS

Glama MCP Gateway

TDQS

Resources