Skip to main content
Glama
Sign In

SEO and Keyword Data API

by com.duoleads.keywords
OverviewDiscussionsAdmin

Clickstream search volume (up to 100 keywords)

clickstream_search_volume
Read-onlyIdempotent

Search volume estimated from clickstream data (real user search behaviour, not Google Ads ranges) for up to 100 keywords: average monthly searches and optional 12-month history, in 94 countries, from clickstream panel data, $0.04 a call. Use when Google Ads volumes look bucketed or you want a second estimate. Keywords under 3 characters are listed in missing. Bad input is a free 400; a data source failure is 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": {
      "keywords": "<keywords>"
    },
    "name": "clickstream_search_volume"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoISO 3166-1 alpha-2 code, used when locationCode is absent (uk = gb).
keywordsYesKeywords (1-100; each 3-80 characters; one that cannot be looked up is listed in missing).
locationCodeNoLocation code of a country (2840 = United States, 2826 = United Kingdom, 2276 = Germany, ...; the /docs table). Default 2840.
includeMonthlyNoAdd each keyword's monthly search volumes.

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?

Goes well beyond the readOnly/openWorld/idempotent annotations: per-call price, x402 USDC-on-Base payment passed in _meta["x402/payment"], free 400 on bad input, no charge on data source failure, and the fact that unlookupable keywords land in a 'missing' list rather than failing the call. The billing and failure semantics are exactly the non-obvious behavior an agent needs before spending money.

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 who it is for, then commercial and failure details. The price is stated twice ('$0.04 a call' and 'Price: $0.04 per successful call, paid over x402'), which is a small redundancy in an otherwise dense, waste-free block.

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 carries the return-shape burden and mostly does: average monthly searches, optional monthly history, a 'missing' list, and country coverage. It stops short of describing the full response structure or pagination/limits beyond keyword count, but for a read-only lookup that is a minor gap.

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%, so the baseline is 3, but the description adds real meaning: the 100-keyword ceiling, the 3-character minimum that routes entries to 'missing', and the optional 12-month history that corresponds to includeMonthly. It does not explain the country vs locationCode precedence beyond what the schema already says.

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 and resource ('search volume estimated from clickstream data') and pins the scope: up to 100 keywords, average monthly searches plus optional 12-month history, 94 countries, clickstream panel source. It explicitly contrasts the data source with Google Ads ranges, so an agent can separate it from google_ads_keywords and keyword_search_volume without opening a schema.

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 a concrete trigger: 'Use when Google Ads volumes look bucketed or you want a second estimate,' which tells the agent when this beats the Ads-based sibling. It never names the sibling tool directly, so the routing hint is a condition rather than an explicit alternative, and there is no when-not-to-use guidance.

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

All SEO and Keyword Data API toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources