Skip to main content
Glama

Get domain DNS popularity

get_domain_popularity

Look up one exact domain in Cloudflare Radar’s global DNS popularity ranking. Returns an exact top-100 rank or a broader popularity group, categories, locations, data dates, and CC BY-NC 4.0 attribution. Not Google SEO difficulty, name competition, or availability. Missing data does not indicate zero competition.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "tld": "<tld>"
    },
    "name": "get_domain_popularity"
  }
}

Input Schema

NameRequiredDescriptionDefault
tldYesOne covered ASCII top-level extension, such as com or .com. Multi-part suffixes and IDNs are not covered.
nameYesOne ASCII domain label without the extension, such as myproject. Price and link tools only build links from it; availability and popularity tools send the exact domain to their providers.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$defs": {
      +    "Error": {
      +      "properties": {
      +        "apiVersion": {
      +          "type": "string"
      +        },
      +        "error": {
      +          "properties": {
      +            "code": {
      +              "type": "string"
      +            },
      +            "message": {
      +              "type": "string"
      +            },
      +            "retryAfterSeconds": {
      +              "minimum": 0,
      +              "type": "number"
      +            }
      +          },
      +          "required": [
      +            "code",
      +            "message"
      +          ],
      +          "type": "object"
      +        }
      +      },
      +      "required": [
      +        "apiVersion",
      +        "error"
      +      ],
      +      "type": "object"
      +    },
      +    "Popularity": {
      +      "properties": {
      +        "apiVersion": {
      +          "type": "string"
      +        },
      +        "bucket": {
      +          "description": "Top-N popularity group, without an exact position inside it. Null does not mean zero competition.",
      +          "enum": [
      +            null,
      +            200,
      +            500,
      +            1000,
      +            2000,
      +            5000,
      +            10000,
      +            20000,
      +            50000,
      +            100000,
      +            200000,
      +            500000,
      +            1000000
      +          ],
      +          "type": [
      +            "integer",
      +            "null"
      +          ]
      +        },
      +        "categories": {
      +          "items": {
      +            "type": "string"
      +          },
      +          "type": "array"
      +        },
      +        "dataPeriod": {
      +          "properties": {
      +            "end": {
      +              "format": "date-time",
      +              "type": "string"
      +            },
      +            "start": {
      +              "format": "date-time",
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "start",
      +            "end"
      +          ],
      +          "type": [
      +            "object",
      +            "null"
      +          ]
      +        },
      +        "domain": {
      +          "type": "string"
      +        },
      +        "expiresAt": {
      +          "description": "Six-hour application cache expiry, not the dataset publication date.",
      +          "format": "date-time",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "fetchedAt": {
      +          "format": "date-time",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "limits": {
      +          "items": {
      +            "type": "string"
      +          },
      +          "type": "array"
      +        },
      +        "message": {
      +          "type": "string"
      +        },
      +        "rank": {
      +          "description": "Exact global DNS popularity rank, only for the top 100. Not a Google rank.",
      +          "maximum": 100,
      +          "minimum": 1,
      +          "type": [
      +            "integer",
      +            "null"
      +          ]
      +        },
      +        "reason": {
      +          "type": "string"
      +        },
      +        "reportedBucket": {
      +          "description": "Provider bucket as supplied, including lower-bound markers such as >200000. A lower bound is not an exact rank or proof of traffic.",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "service": {
      +          "$ref": "#/$defs/ServiceInformation"
      +        },
      +        "source": {
      +          "properties": {
      +            "attribution": {
      +              "type": "string"
      +            },
      +            "documentation": {
      +              "format": "uri",
      +              "type": "string"
      +            },
      +            "id": {
      +              "const": "cloudflare-radar"
      +            },
      +            "license": {
      +              "const": "CC BY-NC 4.0"
      +            },
      +            "licenseUrl": {
      +              "const": "https://creativecommons.org/licenses/by-nc/4.0/"
      +            },
      +            "name": {
      +              "const": "Cloudflare Radar"
      +            },
      +            "url": {
      +              "format": "uri",
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "id",
      +            "name",
      +            "url",
      +            "documentation",
      +            "license",
      +            "licenseUrl",
      +            "attribution"
      +          ],
      +          "type": "object"
      +        },
      +        "status": {
      +          "enum": [
      +            "ranked",
      +            "not_listed",
      +            "unknown"
      +          ],
      +          "type": "string"
      +        },
      +        "topLocations": {
      +          "items": {
      +            "properties": {
      +              "code": {
      +                "type": "string"
      +              },
      +              "name": {
      +                "type": "string"
      +              },
      +              "rank": {
      +                "minimum": 1,
      +                "type": "integer"
      +              }
      +            },
      +            "required": [
      +              "code",
      +              "name",
      +              "rank"
      +            ],
      +            "type": "object"
      +          },
      +          "maxItems": 5,
      +          "type": "array"
      +        }
      +      },
      +      "required": [
      +        "service",
      +        "apiVersion",
      +        "domain",
      +        "status",
      +        "reason",
      +        "message",
      +        "rank",
      +        "bucket",
      +        "reportedBucket",
      +        "categories",
      +        "topLocations",
      +        "dataPeriod",
      +        "fetchedAt",
      +        "expiresAt",
      +        "source",
      +        "limits"
      +      ],
      +      "type": "object"
      +    },
      +    "ServiceInformation": {
      +      "description": "Cheapest Domains identity and optional setup links, separate from upstream evidence. Does not establish client installation or provider health.",
      +      "properties": {
      +        "name": {
      +          "const": "Cheapest Domains"
      +        },
      +        "pluginUrl": {
      +          "format": "uri",
      +          "type": "string"
      +        },
      +        "setupUrl": {
      +          "format": "uri",
      +          "type": "string"
      +        },
      +        "url": {
      +          "format": "uri",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "name",
      +        "url",
      +        "setupUrl",
      +        "pluginUrl"
      +      ],
      +      "type": "object"
      +    }
      +  },
      +  "anyOf": [
      +    {
      +      "$ref": "#/$defs/Popularity"
      +    },
      +    {
      +      "$ref": "#/$defs/Error"
      +    }
      +  ],
      +  "description": "Successful results are Popularity, the REST 200 response; results with isError: true are Error.",
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations it discloses concretely what comes back ('an exact top-100 rank or a broader popularity group'), the third-party source (Cloudflare Radar), and a licensing obligation (CC BY-NC 4.0 attribution). The caveat 'Missing data does not indicate zero competition' is genuinely valuable behavioral context an agent would otherwise misread as a negative signal. Note the annotation readOnlyHint=false sits slightly at odds with a pure 'look up' framing, though the description itself makes no write claims and this reads as a conservative default rather than a contradiction.

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?

Four compact sentences, front-loaded with purpose, then return shape, then disambiguation, then the caveat. The negation list is a high-density way to fence off siblings and nothing is redundant.

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 the description need not spell out return fields, and the licensing, data-source, and missing-data caveats cover the non-obvious gaps. It does not say how unsupported TLDs or out-of-ranking domains surface (error vs. empty response), which leaves a small but real ambiguity for a two-parameter lookup.

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 coverage is 100% and both parameters already document the ASCII label/extension split, length limits, and IDN exclusions. The description only adds the 'one exact domain' constraint (no wildcards, no batch), which is marginal beyond what the schema already carries, so the 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 ('Look up one exact domain in Cloudflare Radar's global DNS popularity ranking') and immediately differentiates itself from siblings by denying the adjacent concepts of SEO difficulty, name competition, and availability. An agent can distinguish it from check_availability, compare_domain_names, and get_naming_guidance 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 Guidelines4/5

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

'Look up one exact domain' plus the explicit 'Not ... availability' clause makes the selection context clear and steers away from the availability/competition tools. It stops short of naming siblings explicitly or stating what to do for multiple domains (there is a batch sibling for availability but none for popularity), so it is clear guidance without full routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.