audit.domains - Domain Valuation

Search domains for sale

search_domain_listings

Read-onlyIdempotent

Filter, sort and page the domains listed for sale by their DNS-verified owners; each listing has a fixed price, the appraisal with its range and a buy link. Set mode to changes to get listings listed, changed or removed since a cursor, and poll that instead of re-searching. Use ask_domain_market instead to search from a plain sentence, and quote_domain_purchase for the live terms of one listing. Reads live inventory, runs no appraisal and changes nothing. No matches returns an empty list.

Input Schema

Name	Required	Description
`q`	No	Part of the domain name to match.
`tld`	No	Suffix without the dot, such as com or io.
`mode`	No	search (default) filters live inventory. changes returns listings listed, changed or removed since cursor.
`sort`	No	Result order. Defaults to newest.
`limit`	No	Listings per page, 1 to 100.
`cursor`	No	For mode changes: the cursor from the previous reply. Omit it for the last 24 hours.
`offset`	No	Listings to skip, for paging.
`maxLength`	No	Maximum length of the name, 1 to 63 characters.
`acceptsOffers`	No	true returns only listings that accept offers; false returns only fixed-price listings.
`maxPriceCents`	No	Maximum fixed price in US cents.
`minPriceCents`	No	Minimum fixed price in US cents.

Output Schema

Name	Required	Description
`count`	No
`total`	No
`cursor`	No
`events`	No
`hasMore`	No
`listings`	No
`advertised`	No	The same filters over names their owners advertise for sale in their own DNS (RFC 10023 _for-sale), from the last scan. Not listings here: the price is indicative and buyUrl is the owner's. Null when acceptsOffers is set.
`nextOffset`	No
`generatedAt`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 20, 2026

addedOutput schema / properties / advertised

Added value: +{
+  "description": "The same filters over names their owners advertise for sale in their own DNS (RFC 10023 _for-sale), from the last scan. Not listings here: the price is indicative and buyUrl is the owner's. Null when acceptsOffers is set.",
+  "properties": {
+    "checkedOn": {
+      "format": "date",
+      "type": "string"
+    },
+    "names": {
+      "items": {
+        "properties": {
+          "appraisalUrl": {
+            "type": "string"
+          },
+          "askUsd": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "buyUrl": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "domain": {
+            "type": "string"
+          },
+          "recordUrl": {
+            "type": "string"
+          },
+          "sellerHost": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "nextOffset": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "note": {
+      "type": "string"
+    },
+    "total": {
+      "type": "integer"
+    }
+  },
+  "type": [
+    "object",
+    "null"
+  ]
+}

Changed14 schema fields changedOct 6, 2026

addedInput schema / properties / acceptsOffers / description

Added value: +"true returns only listings that accept offers; false returns only fixed-price listings."

addedInput schema / properties / cursor

Added value: +{
+  "description": "For mode changes: the cursor from the previous reply. Omit it for the last 24 hours.",
+  "type": "string"
+}

addedInput schema / properties / limit / description
```
Added value: +"Listings per page, 1 to 100."
```

addedInput schema / properties / maxLength / description

Added value: +"Maximum length of the name, 1 to 63 characters."

addedInput schema / properties / maxPriceCents / description
```
Added value: +"Maximum fixed price in US cents."
```
addedInput schema / properties / minPriceCents / description
```
Added value: +"Minimum fixed price in US cents."
```

addedInput schema / properties / mode

Added value: +{
+  "description": "search (default) filters live inventory. changes returns listings listed, changed or removed since cursor.",
+  "enum": [
+    "search",
+    "changes"
+  ],
+  "type": "string"
+}

addedInput schema / properties / offset / description
```
Added value: +"Listings to skip, for paging."
```

changedInput schema / properties / q / description

Previous value: -"Part of the domain name."New value: +"Part of the domain name to match."

addedInput schema / properties / sort / description

Added value: +"Result order. Defaults to newest."

changedInput schema / properties / tld / description

Previous value: -"Suffix such as com or io."New value: +"Suffix without the dot, such as com or io."

addedOutput schema / description

Added value: +"mode search: listings, count, total, nextOffset. mode changes: events, cursor (send back), hasMore."

addedOutput schema / properties

Added value: +{
+  "count": {
+    "type": "integer"
+  },
+  "cursor": {
+    "type": "string"
+  },
+  "events": {
+    "items": {
+      "properties": {
+        "at": {
+          "type": "string"
+        },
+        "domain": {
+          "description": "Delisted only.",
+          "type": "string"
+        },
+        "id": {
+          "type": "string"
+        },
+        "listing": {
+          "description": "As above; not on delisted.",
+          "type": "object"
+        },
+        "type": {
+          "enum": [
+            "listed_or_updated",
+            "delisted"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "type",
+        "at"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "generatedAt": {
+    "format": "date-time",
+    "type": "string"
+  },
+  "hasMore": {
+    "type": "boolean"
+  },
+  "listings": {
+    "items": {
+      "description": "Appraisal fields are null when the seller listed by DNS with no appraisal.",
+      "properties": {
+        "autoAccept": {
+          "type": "boolean"
+        },
+        "buyUrl": {
+          "type": "string"
+        },
+        "domain": {
+          "type": "string"
+        },
+        "fairUsd": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "highUsd": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "lowUsd": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "priceCents": {
+          "type": "integer"
+        },
+        "priceToFairRatio": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "quoteUrl": {
+          "type": "string"
+        },
+        "verifiedAt": {
+          "type": "string"
+        },
+        "withinModelRange": {
+          "type": [
+            "boolean",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "domain",
+        "priceCents",
+        "buyUrl"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "nextOffset": {
+    "type": [
+      "integer",
+      "null"
+    ]
+  },
+  "total": {
+    "type": "integer"
+  }
+}

addedOutput schema / required
```
Added value: +[
+  "generatedAt"
+]
```

First observedSep 30, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered; the description still adds value by stating it reads live inventory, runs no appraisal, changes nothing, and returns an empty list on no matches. The main behavioral gap is that polling cadence/rate expectations for the changes mode are not described.

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 with the core action and scope, then progressively adds mode behavior, alternatives and guarantees in a compact paragraph with no filler. It is slightly dense for a single sentence-chain, but every clause carries information.

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 11 optional parameters, an output schema present, and full annotation coverage, the description covers the essentials: what it searches, how to page/poll, what a listing contains, and that it is a pure read. Minor gaps remain around paging interaction between offset and cursor, but nothing needed to invoke it correctly is missing.

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% and the schema already explains every parameter, including cursor semantics for mode=changes and the cents units for price bounds. The description's mode/cursor discussion largely restates what the schema provides, so it lands at the baseline rather than adding new parameter meaning.

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 set (filter, sort, page) over a specific resource (domains listed for sale by DNS-verified owners), including the distinctive scope that these are verified owner listings with fixed prices and appraisals. It names the sibling tools it is not (ask_domain_market, quote_domain_purchase), so an agent can disambiguate without opening any 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 explicit routing rules: use ask_domain_market for a plain-sentence search, quote_domain_purchase for the live terms of a single listing, and switch to mode=changes with polling instead of re-searching. The when-to-use and when-to-use-something-else conditions are both spelled out.

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

All audit.domains - Domain Valuation 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.

Resources

Need Help?