Skip to main content
Glama

Keyword TLD Popularity Check

bulk_tld
Read-onlyIdempotent

For up to 50 keywords, count how many TLDs each exact name is registered in (keyword.tld), among the TLDs DomainKits tracks, split into popular TLDs, country-code TLDs, and other gTLDs. Returns counts only: it does not list individual TLDs, check availability, or report sale status.

Related: tld_check (per-TLD status for one keyword), bulk_available (status of specific domains).

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": {
      "keywords": "<keywords>"
    },
    "name": "bulk_tld"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordsYesComma-separated keywords to check (max 50)

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNo
totalNoNumber of keywords checked
successNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / required
      Removed value: -[
      -  "success"
      -]
  2. Changed4 schema fields changed
    • changedOutput schema / properties / data / items / properties / cctld / description
      Previous value: -"Count in country-code TLDs"New value: +"Count in country-code TLDs outside the popular set"
    • changedOutput schema / properties / data / items / properties / other / description
      Previous value: -"Count in other gTLDs"New value: +"Count in other gTLDs outside the popular set"
    • changedOutput schema / properties / data / items / properties / popular / description
      Previous value: -"Count in popular TLDs (com, net, org, io, ai, app, etc.)"New value: +"Count in popular TLDs (com, net, org, io, ai, app, and similar; io and ai count here, not in cctld)"
    • changedOutput schema / properties / data / items / properties / total / description
      Previous value: -"Total TLDs with this keyword registered"New value: +"Number of TLDs where keyword.tld is registered (popular + cctld + other)"
  3. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare this as a read-only, idempotent, non-destructive operation. Beyond that, the description adds important behavioral scope: it counts registrations only among DomainKits-tracked TLDs, returns counts rather than lists, and does not check availability or sale status.

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?

The description is front-loaded with the core counting behavior, then states limitations and related tools in a compact related-tools line. There is no unnecessary wording.

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

Completeness5/5

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

For a one-parameter bulk counting tool with full schema coverage, annotations, and an output schema, the description supplies what an agent needs: input limit, counted entity, grouping, return-value nature, exclusions, and sibling alternatives.

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 the single keywords parameter already documents that it is comma-separated with a maximum of 50. The description reinforces the 50-keyword limit and exact-name behavior but adds little syntax or format detail beyond the schema.

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?

The description states a specific verb and resource: count how many tracked TLDs each exact keyword is registered in. It also explains the grouping into popular TLDs, ccTLDs, and other gTLDs, and explicitly distinguishes the result from per-domain status tools.

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?

It names the relevant alternatives (tld_check and bulk_available) and clarifies what this tool does not do: list individual TLDs, check availability, or report sale status. That gives clear routing guidance between the bulk count tool and per-domain status tools.

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.