Popdot AI

search_domains

Read-only

Search domains available for rent on Popdot AI. Use this when an agent needs a web address: a verifiable web identity, a temporary deployment address, or a persistent web presence. Returns domains with pricing, tier, and availability. No auth required. Your first subdomain is free for 24 hours: pick a domain marked trialEligible and call try_domain instead of paying.

Input Schema

Name	Required	Description
`limit`	No	Maximum number of results to return (default: 20, max: 50)
`query`	No	Search query to match against domain names, tags, and categories
`emotion`	No	Filter by the reaction the domain is built to elicit: comedy, absurd, playful, edgy, wholesome, professional, trustworthy. Unknown values are ignored.
`maxPrice`	No	Maximum daily price in USD
`minPrice`	No	Minimum daily price in USD

Output Schema

Name	Required	Description	Default
`domains`	Yes
`freeTrial`	No
`pagination`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 28, 2026

addedOutput schema / properties / domains / items / properties / trialEligible
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / freeTrial

Added value: +{
+  "properties": {
+    "available": {
+      "type": "boolean"
+    },
+    "duration": {
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    },
+    "requires": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "tool": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedAug 27, 2026

addedOutput schema / properties / pagination / properties

Added value: +{
+  "limit": {
+    "type": "number"
+  },
+  "page": {
+    "type": "number"
+  },
+  "total": {
+    "type": "number"
+  },
+  "totalPages": {
+    "type": "number"
+  }
+}

Changed1 schema field changedAug 26, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "domains": {
+      "items": {
+        "properties": {
+          "emotionTags": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "fullDomain": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "pricing": {
+            "properties": {
+              "currency": {
+                "type": "string"
+              },
+              "daily": {
+                "type": "number"
+              },
+              "hourly": {
+                "type": "number"
+              },
+              "monthly": {
+                "type": "number"
+              },
+              "weekly": {
+                "type": "number"
+              }
+            },
+            "type": "object"
+          },
+          "tier": {
+            "type": "string"
+          },
+          "tierScore": {
+            "type": "number"
+          },
+          "tld": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "pagination": {
+      "type": "object"
+    }
+  },
+  "required": [
+    "domains"
+  ],
+  "type": "object"
+}

Changed1 schema field changedAug 26, 2026

addedInput schema / properties / emotion

Added value: +{
+  "description": "Filter by the reaction the domain is built to elicit: comedy, absurd, playful, edgy, wholesome, professional, trustworthy. Unknown values are ignored.",
+  "enum": [
+    "comedy",
+    "absurd",
+    "playful",
+    "edgy",
+    "wholesome",
+    "professional",
+    "trustworthy"
+  ],
+  "type": "string"
+}

First observedJul 27, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With readOnlyHint and openWorldHint already declared, the description still adds real value: "No auth required" removes an auth preflight, and it discloses that results carry pricing, tier, and availability. The 24-hour free trial and the trialEligible marker are non-obvious behavioral facts an agent could not infer from structured fields, though rate limits and result-set size behavior are unstated.

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?

Purpose is front-loaded in the first clause, then use cases, then return shape, auth, and the trial routing — a sensible priority order with no filler sentences. Slightly dense packing of the trial instruction into one long final sentence costs it a point.

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?

An output schema exists, so describing return contents is a bonus rather than a requirement, and the description covers the essentials for a five-param read-only search: no auth, what comes back, and how to act on trial-eligible results. What's missing is any hint about result volume or pagination beyond the limit parameter, and how its output feeds rent_domain or check_availability.

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 limit, query, emotion, maxPrice, and minPrice are already fully documented including the default/max on limit and the ignore-unknown-values behavior on emotion. The description adds no parameter-level syntax beyond what the schema provides; its only field reference (trialEligible) is a return value, not an input. Baseline 3 applies.

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 and resource ("Search domains available for rent") and immediately scopes it with concrete agent-facing use cases (verifiable identity, temporary deployment, persistent presence). It also names a sibling tool (try_domain) with the condition that selects it, so an agent can tell this apart from the rental path without opening a schema.

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?

Gives explicit when-to-use framing ("Use this when an agent needs a web address") plus three concrete scenarios, and routes trial-eligible picks to try_domain. It stops short of explaining how this relates to the other siblings — check_availability, get_price_quote, rent_domain — which is the natural next question after searching.

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

All Popdot AI 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.