Skip to main content
Glama
Sign In

SEO and Keyword Data API

by com.duoleads.keywords
OverviewDiscussionsAdmin

Competitor domains (up to 100)

competitor_domains
Read-onlyIdempotent

Competitor domains: the websites competing with a domain in Google organic search, each with the keywords both rank for, the average position on them, and the competitor's total ranking keywords and estimated traffic; up to 100 in one $0.048 call. Use when you need to find a site's real SEO competitors (bare domain; www. is dropped). 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": "competitor_domains"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum competitors 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.1/5.0
Behavior5/5

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

Goes well beyond the annotations with material behavior: cost per call, that no-data results are empty but still charged, that bad input is free, that upstream errors are not charged, and the x402/USDC-on-Base payment handshake via _meta. Read-only and idempotent hints are already covered by annotations, but the billing and failure semantics here are exactly the context an agent cannot get elsewhere.

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-loads the resource definition, then usage, then cost/behavior. Information-dense with little filler, though the $0.048 price is repeated twice ('up to 100 in one $0.048 call' and again in the closing price sentence), which is mild redundancy.

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?

No output schema exists, yet the description still enumerates what each result contains, states the 100-result cap, documents default behavior via the schema, and covers billing and payment mechanics. For a paid, read-only, open-world lookup with five parameters, nothing an agent needs to call it correctly is missing.

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 five parameters are already documented in detail, including the country/locationCode/languageCode fallback rules. The description only restates the bare-domain/www rule and repeats the 100 cap already implied by the limit maximum. Baseline 3 is appropriate since the schema does the heavy lifting.

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 resource with a concrete definition: websites competing with a domain in Google organic search, and enumerates the returned fields (shared keywords, average position, competitor keyword total, estimated traffic). It does not explicitly contrast itself with the similar siblings serp_competitors or keyword_gap, so an agent must infer the distinction from the 'organic keyword overlap' framing.

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 clear use case: 'Use when you need to find a site's real SEO competitors.' It also specifies input hygiene (bare domain, www. dropped). It does not state when NOT to use it or name an alternative tool, so selection among competitors-related siblings is left to inference.

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