Skip to main content
Glama

Keyword Registration Trends

keywords_trends
Read-onlyIdempotent

Return provider-computed keyword registration statistics. hot and emerging cover rolling keyword cohorts; prefix returns prefix activity buckets. scope=all represents the provider's filtered all-gTLD sample, while scope=com represents its pure-letter .com subset and is not available for prefix. Results are representative samples, not a complete registry feed, demand measurement, valuation, or investment recommendation.

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": "keywords_trends"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoTrend dataset to return.
scopeNoall = filtered all-gTLD sample; com = pure-letter .com subset. prefix supports all only.

Output Schema

NameRequiredDescriptionDefault
dataNo
typeNo
errorNoError message when success is false.
scopeNo
totalNo
successNo
coverageNoProvider coverage identifier, such as all_gTLDs or com_letters_only.
data_dateNoProvider data date when supplied; not derived from the request time.
updated_atNoProvider update timestamp when supplied; not derived from the request time.
sample_typeNoProvider sampling description, such as filtered_representative_sample.
window_daysNoProvider-defined rolling observation window when supplied.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / required
      Removed value: -[
      -  "success"
      -]
  2. Changed2 schema fields changed
    • changedOutput schema / properties / data_date / description
      Previous value: -"Provider data date when supplied; never synthesized from request time."New value: +"Provider data date when supplied; not derived from the request time."
    • changedOutput schema / properties / updated_at / description
      Previous value: -"Provider update timestamp when supplied; never synthesized from request time."New value: +"Provider update timestamp when supplied; not derived from the request time."
  3. Changed2 schema fields changed
    • changedOutput schema / properties / data / items / properties / top_registrar / description
      Previous value: -"Deprecated Top-1 compatibility field used by the current Gateway until it passes top_registrars through unchanged."New value: +"Deprecated: the first entry of top_registrars, kept for compatibility."
    • changedOutput schema / properties / data / items / properties / top_registrars / description
      Previous value: -"Provider-computed registrar ranking. MCP does not derive this from nrds."New value: +"Registrar ranking computed by the data source; not derived from nrds."
  4. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the burden is lighter. The description adds genuinely non-redundant context: results are representative provider samples, not a full registry feed or a demand/valuation/investment signal, which sets the agent's expectations about coverage and interpretation. Pagination and result-size behavior remain unstated, though the output schema likely covers shape.

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?

Three dense sentences, front-loaded with the core action and followed by dataset and scope semantics, with no filler. The closing disclaimer sentence is long but earns its place by preventing misuse of the numbers; trimming it slightly would not hurt.

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?

With only two optional enum parameters and an output schema present, the remaining risk is interpretive, and the description addresses exactly that via the sampling caveat and the scope restriction on prefix. Nothing an agent needs in order to call this correctly or interpret its output appears to be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and both parameters have enum value descriptions, so the baseline is already 3. The description goes beyond the schema by explaining what the cohorts mean (rolling cohorts for hot/emerging, activity buckets for prefix) and clarifying that scope=all is a filtered all-gTLD sample while com is a pure-letter subset.

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 verb and resource ("Return provider-computed keyword registration statistics") and enumerates the three datasets (hot, emerging, prefix), which makes the tool's scope legible. It does not explicitly contrast with adjacent siblings such as tld_trends or keyword_data, so the reader must infer the keyword-level vs TLD-level distinction from the wording alone.

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?

Gives useful usage constraints — scope=com is unavailable for prefix, and hot/emerging cover rolling cohorts while prefix returns buckets — which effectively tells the agent which parameter combinations are valid. It does not say when to choose this tool over a sibling trend or keyword tool, so selection guidance is implied rather than stated.

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.