Skip to main content
Glama
apexseo-geo-mcp

apexseo-geo-mcp

Live Head-to-Head Competitor GEO Benchmark ($0.05)

geo_competitor_compare
Read-onlyIdempotent

Benchmark your target URL against 1-3 competitors with live GEO and AI-crawler audits, then get exact win/loss deltas and a ranked ICE counter-strategy roadmap.

Instructions

Runs parallel live page GEO audits and AI-crawler (robots.txt / llms.txt) checks across your targetUrl and 1-3 competitorUrls, computing exact win/loss deltas across geoScore, AI-crawler readiness, TTFB speed, schema depth, question headings, and llms.txt coverage, plus a ranked ICE counter-strategy roadmap.

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": {
      "targetUrl": "<targetUrl>",
      "competitorUrls": "<competitorUrls>"
    },
    "name": "geo_competitor_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetUrlYesYour target URL to benchmark.
competitorUrlsYes1 to 3 competitor URLs for live head-to-head benchmarking.

Output Schema

NameRequiredDescriptionDefault
targetYes
competitorsYes
gapsToCloseNo
iceActionPlanYes
advantagesToPressNo
deltasVsCompetitorBestYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the description needn't restate safety. It adds real value beyond them: the audits are 'live' and run 'in parallel' (network dependency and latency implication), cover robots.txt and llms.txt crawler access, and return computed deltas plus a ranked counter-strategy roadmap. It does not disclose cost or rate/credit limits, which the title hints at but the description omits.

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 the action and scoped by URL arguments, so the agent reads the essential operation first. It is a single very dense sentence packed with a seven-item metric list, which borders on run-on but every clause carries a distinct output fact.

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?

An output schema exists, and annotations cover the safety profile for a read-only tool, so return-value explanation is not required. The description still supplies the metric set and roadmap output, plus the live/parallel execution model, leaving nothing essential missing for correct invocation.

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% and both parameters are fully documented in the schema, including the 1-3 item array bound. The description restates this ('targetUrl and 1-3 competitorUrls') without adding format, normalization, or error-handling detail, so the 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?

States a specific verb and resource — parallel live GEO audits plus AI-crawler checks across a target and 1-3 competitors, with win/loss deltas and an ICE roadmap. The comparative scope ('head-to-head' across targetUrl and competitorUrls) separates it from single-page siblings like geo_page_audit and ai_crawler_audit without needing to name them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the framing: use it when you want a competitive benchmark rather than a solo audit. There is no explicit when-to-use trigger, no when-not condition, and no alternative tool named for the single-page case, leaving the agent to infer routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.