Skip to main content
Glama

SEO Rank Fixer

Competitor overview

competitor_overview
Read-onlyIdempotent

Any website's estimated Google footprint, from a third-party data provider (DataForSEO, modelled from Google results, not the site's own analytics): estimated monthly Google traffic, how many keywords it ranks for (top 3, 4-10, 11-100), its Authority score when known, its top pages (estimated traffic, keywords) and top keywords (position, monthly searches, ranking URL). With a siteId, the numbers are for that site's country and the user's own site is given side by side. A domain looked up in the last 7 days is reused at no cost; a new one uses one of the workspace's daily lookups (the reply says how many are left). Nothing on any site is changed.

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": {
      "domain": "<domain>"
    },
    "name": "competitor_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesThe website to look up, e.g. competitor.com.
siteIdNoA site id from list_sites, to compare with and to use its country. Optional: the United States without one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well past the readOnly/openWorld annotations: discloses the third-party data source and its modelling caveat, the 7-day cache with free reuse, per-workspace daily lookup consumption with remaining quota reported in the reply, and that nothing is changed on any site. These are exactly the operational facts an agent needs before spending quota.

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 core purpose, then layers data contents, siteId behavior and cost/caching rules in a logical order, closing with a safety statement. The parenthetical enumerations (top 3/4-10/11-100, position/searches/URL) make it dense, but each clause carries information rather than filler.

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 enumerates the returned sections — traffic estimate, keyword counts by bucket, Authority score, top pages with traffic and keywords, top keywords with position, volume and ranking URL — plus the caveat that Authority may be missing. Combined with the quota and caching notes, an agent can call it correctly and interpret the reply.

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 both parameters are already documented, making 3 the baseline. The description does add real meaning for siteId — it selects the comparison site and drives the country of the numbers, with United States as the fallback — but adds nothing to the domain parameter beyond the schema example.

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?

Names the exact resource and metric set: estimated Google footprint for any website, including traffic, keyword buckets, Authority score, top pages and top keywords. It also declares the data provenance (DataForSEO, modelled from Google results, not the site's own analytics), which sharply distinguishes it from first-party analytics siblings like site_performance.

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?

Explains the siteId case (compare with the user's own site, use that site's country, default United States) and gives the cost condition — 7-day reuse is free, a new domain consumes a daily lookup. It stops short of naming an alternative such as competitor_gap for gap analysis, so there are no explicit when-not rules.

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.