Skip to main content
Glama

NetAPI Top 1M most popular domains (slice)

top_1m
Read-onlyIdempotent

Retrieve a rank-ordered slice of popular domains to check domain popularity and paginate through results using limit and offset controls.

Instructions

A slice of the NetAPI Top 1 Million most popular domains, ordered by rank. The complete list is a free daily CSV (https://netapi.com/netapi_top1mln.csv, CC BY 4.0). Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "top_1m"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows to return (default 10, max 100 without an account)
offsetNoRank to start after (default 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive, so the safety profile is covered. The description adds useful context (snapshot of a ranked list, free, full CSV available at a URL) but omits any pagination/rate-limit or freshness behavior beyond 'daily CSV'.

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?

Two tight sentences with the core identity front-loaded and zero filler. The CSV/link sentence earns its place by pointing to the full dataset, though it is arguably extraneous detail for the tool call itself.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description could clarify the return shape (domains plus rank field), which it only hints at via 'ordered by rank'. It is adequate for a simple paginated list tool, but leaves the response format to inference.

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 and offset (including the 'max 100 without an account' constraint) are fully documented in the schema. The description adds nothing about the parameters, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (a slice of the NetAPI Top 1M popular domains) plus ordering (by rank) and the licensing/free status. However it does not differentiate from siblings like top_websites or domain_rank, so an agent must infer which ranked-list tool to pick.

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 only implied: it hints that for the complete list you should use the free daily CSV instead, which is a partial alternative. There is no explicit when-to-use-this-vs-siblings guidance (top_websites, domain_rank) and no stated prerequisites.

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