Skip to main content
Glama

SEO Rank Fixer

Competitor gap

competitor_gap
Read-onlyIdempotent

Searches a competitor ranks for in Google's top 20 that the site does not rank for, from the latest stored competitor gap report: search volume, keyword difficulty (0-100), search intent, the competitor's position and ranking page, best opportunity first, branded searches removed. Read-only: it never fetches a new report (the user runs those in SEO Rank Fixer).

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": {
      "siteId": "<siteId>"
    },
    "name": "competitor_gap"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYesA site id from list_sites.
competitorNoA competitor's domain, e.g. example.com. Optional: the most recent report when left empty.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, yet the description still adds substantive behavior: results come from a cached report rather than a live crawl, are ordered best-opportunity-first, exclude branded searches, and carry volume, difficulty, intent, competitor position and ranking page. That staleness and ordering information is not derivable from any structured field.

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?

Two sentences, the primary capability front-loaded and the freshness caveat immediately after. It is dense but earns its length; the opening clause ('Searches a competitor ranks for in Google's top 20 that the site does not rank for') is grammatically tangled and could be tightened.

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?

For a two-parameter read tool with no output schema, the description supplies the returned columns, the sort order, the branded-search exclusion and the report freshness caveat, which is everything an agent needs to interpret results 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%, with siteId pointing at list_sites and competitor documented as optional with its empty-value behavior, so the schema carries the parameter burden. The description adds only a restatement that the competitor filter is by domain scope; baseline 3 applies.

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 a specific verb and resource ('Searches a competitor ranks for in Google's top 20 that the site does not rank for') and pins the data source to the latest stored competitor gap report. The read-only clause distinguishes it from a report-generation sibling, so an agent can tell what it does without opening the 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?

Explicitly states the condition the tool does not cover — 'it never fetches a new report (the user runs those in SEO Rank Fixer)' — which steers the agent away from expecting fresh data. It stops short of naming which MCP sibling to call instead, so the alternative routing is implied rather than spelled out.

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.