Skip to main content
Glama

SEO and Keyword Data API

Keywords for a site or page (up to 100)

keywords_for_site
Read-onlyIdempotent

Keyword suggestions for a website or one page: the Google searches relevant to it, each with search volume, CPC, competition, keyword difficulty and search intent; up to 100 in one $0.04 call (Google Ads data). Use when you need keyword ideas from a domain (www. is dropped) or a page URL. A site with no data returns empty results (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": {
      "target": "<target>"
    },
    "name": "keywords_for_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum keywords to return (1-100). Defaults to 20.
targetYestargetType site: a bare domain like example.com (no scheme or path; a leading www. is dropped). targetType page: an absolute http(s) page URL.
countryNoOptional ISO 3166-1 alpha-2 code or country name, used when locationCode is absent (uk = gb).
targetTypeNoSuggest keywords for the whole site (default) or only the target page.
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.1/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, open-world, but the description goes well beyond them: cost per successful call, the x402/USDC-on-Base payment flow with the exact _meta["x402/payment"] key, the fact that empty results are still billed, and which failure classes are free. Those billing and invocation mechanics are exactly what an agent cannot infer from annotations.

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 purpose, then return fields, then usage condition, then billing mechanics — every sentence is load-bearing. It is dense (four clauses of pricing in one paragraph) but nothing is redundant.

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 no output schema, the description compensates by listing the returned metrics, and it covers cost, payment transport, empty-result behavior, and error charging. An agent has everything needed to choose the tool and pay for the call correctly.

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 all six parameters (including targetType enum, locationCode, languageCode fallbacks) are already documented in the schema. The only description-side parameter detail is 'www. is dropped', which the schema also states. Baseline 3 is appropriate when the schema carries the load.

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?

The description gives a specific verb and resource ('keyword suggestions for a website or one page') plus an enumeration of returned fields (volume, CPC, competition, difficulty, intent), and the site-vs-page input distinction implicitly separates it from seed-keyword siblings like keyword_ideas or related_keywords. It stops short of naming an alternative explicitly, which keeps it from a 5.

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?

'Use when you need keyword ideas from a domain (www. is dropped) or a page URL' states a clear selection condition, and the charging rules ('A site with no data returns empty results (still charged). Bad input is free; upstream errors are not charged') tell the agent when the call is wasteful. No explicit when-not or named-alternative guidance is given, so the exclusions needed for a 5 are absent.

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.