Skip to main content
Glama
Sign In

SEO and Keyword Data API

by com.duoleads.keywords
OverviewDiscussionsAdmin

Top pages of a domain (up to 100)

relevant_pages
Read-onlyIdempotent

Relevant pages: a domain's pages that get the most Google search traffic, each with its organic and paid ranking keywords, estimated monthly traffic, ad value and top-3/10/100 counts; up to 100 pages in one $0.048 call. Use when you need a site's top SEO pages (bare domain; www. is dropped). A domain with no data returns empty results (still charged). Bad input is free; upstream errors are not charged. Price: $0.048 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": "relevant_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum pages to return (1-100). Defaults to 20.
targetYesBare domain like example.com (no scheme, path or port; a leading www. is dropped).
countryNoOptional ISO 3166-1 alpha-2 code or country name, used when locationCode is absent (uk = gb).
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.3/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, yet the description adds substantial non-obvious behavior: per-call pricing, that empty results are still charged, that bad input is free and upstream errors are not, and that payment goes in _meta['x402/payment'] via USDC on Base. Those are exactly the facts an agent needs before spending money on a call.

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 and returned content, then constraints and pricing. Minor inefficiency: the $0.048 price appears twice ('one $0.048 call' and 'Price: $0.048 per successful call'), and the billing sentences could be tightened.

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?

A five-parameter paid query tool with no output schema, and the description covers what comes back, the domain format, and the billing contract well. It stops short of describing pagination/truncation behavior when limit < available pages or typical result ordering.

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%, so the schema already documents limit, target, country, languageCode and locationCode, including fallback semantics. The description only echoes the bare-domain/www rule already present in the target field, adding no new meaning for the market/fallback parameters. Baseline 3.

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 ('a domain's pages that get the most Google search traffic') and enumerates the returned fields (keywords, traffic, ad value, top-3/10/100 counts), so an agent can distinguish it from sibling tools like ranked_keywords or keywords_for_site 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?

'Use when you need a site's top SEO pages' gives a clear condition, and the bare-domain rule plus empty-result/pricing notes set expectations. However, it never names when NOT to use it or which sibling (e.g. ranked_keywords, domain_overview, traffic_estimate) covers adjacent needs.

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