Skip to main content
Glama

SEO and Keyword Data API

Traffic estimate (up to 100 domains)

traffic_estimate
Read-onlyIdempotent

Traffic estimate for up to 100 domains in one $0.04 call: each domain's estimated monthly organic and paid visits from Google (etv) and its count of ranking keywords. Use when you need to compare the search traffic of many websites at once (bare domains; www. is dropped). A domain with no data gives found false (still charged). Bad input is free; upstream errors are not charged. Price: $0.04 per successful call, paid over x402 (USDC on Base); pass the payment in _meta["x402/payment"].

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": {
      "targets": "<targets>"
    },
    "name": "traffic_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoOptional ISO 3166-1 alpha-2 code or country name, used when locationCode is absent (uk = gb).
targetsYesBare domains (1-100) like example.com; no scheme or path; a leading www. is dropped.
languageCodeNoLanguage code (2-letter). Defaults to en. An unsupported location falls back to 2840 (United States) with en (or the requested language if the United States offers it); a supported location with a language it does not offer uses that location's default language (en if offered). Either way market.fallback is true and market.warnings says what was used.
locationCodeNoGoogle Ads location code (geo target ID). Defaults to 2840 (United States); an unsupported code falls back to 2840 (United States, market.fallback).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare read-only/open-world/idempotent, so the description carries the rest and does so richly: exact price ($0.04 per successful call), the x402/USDC-on-Base payment channel via _meta["x402/payment"], and a charge policy distinguishing bad input (free) from upstream errors (not charged) from no-data domains (found false, still charged). That billing and failure semantics are precisely the kind of context annotations cannot convey.

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?

Front-loaded with what the tool returns and when to use it, and every clause carries information (scope, normalization, charge rules, price, payment mechanism). It is dense but not padded, though the pricing/payment material is crammed into the tail rather than separated, which slightly hurts scanability.

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 no output schema, the description does most of the work: it names the returned metrics, the found-flag semantics, and the market.fallback/market.warnings signals. It stops short of describing the result envelope (per-domain array shape, error payloads), leaving a modest gap for a batch tool.

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 already 100%, so the baseline is 3; the description adds value by documenting the out-of-schema payment parameter (_meta["x402/payment"]) and reinforcing the target normalization rule. It does not explain country/locationCode interaction beyond what the schema already states, so it stops short of a 5.

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+scope: 'Traffic estimate for up to 100 domains in one call', and enumerates exactly what is returned (estimated monthly organic and paid visits from Google via etv, plus ranking keyword count). The phrase 'compare the search traffic of many websites at once' implicitly separates it from single-domain siblings like domain_overview.

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?

Gives clear triggering context ('Use when you need to compare the search traffic of many websites at once') and input preconditions (bare domains, www. dropped, max 100). It does not name an alternative sibling for the single-domain case or state when not to use it, so it falls short of a 5.

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.