Skip to main content
Glama

Popularity rank of a domain (NetAPI Top 1M)

domain_rank
Read-onlyIdempotent

Check a domain's popularity position in the NetAPI Top 1 Million and its rank within its TLD, based on daily SEO, link-graph, and traffic signals.

Instructions

Position of a domain in the NetAPI Top 1 Million most popular domains (1 = most popular) and its rank inside its own TLD. Rebuilt daily from SEO / link-graph and traffic signals. Free.

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": {
      "domain": "<domain>"
    },
    "name": "domain_rank"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name, e.g. "github.com"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 safety is covered. The description adds genuinely non-structured context: the ranking is rebuilt daily and derived from SEO/link-graph and traffic signals, which tells the agent the value is fresh but approximate and third-party sourced. It stops short of saying what happens for domains outside the top 1M.

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?

Two sentences, front-loaded with what is returned, followed by data provenance and freshness. No filler; even the one-word 'Free.' carries decision-relevant 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?

For a one-parameter read tool with full annotation coverage, the description covers what is returned, how the data is built, and how often it refreshes. Remaining gaps are edge-case behavior (domain absent from the top 1M) and any rate limits, which are minor here.

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?

Only one parameter exists and schema coverage is 100%, with the schema itself supplying the format example 'github.com'. The description adds no extra syntax or constraint detail beyond that, 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+resource: the rank position of a domain in the NetAPI Top 1M, plus its rank within its own TLD. This cleanly distinguishes it from sibling list tools like top_1m and top_websites, which return lists rather than a single domain's position.

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?

Usage is implied by the query semantics (give a domain, get its rank), and 'Free' signals there is no cost barrier. However, no when-to-use condition or alternative is named — nothing tells the agent to prefer top_1m for enumerating the list versus this tool for scoring a known domain.

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