Skip to main content
Glama

ApexSEO GEO & AI-Crawler Audit MCP

Live GEO / AEO & Technical SEO Page Audit ($0.02)

geo_page_audit
Read-onlyIdempotent

Performs a comprehensive live technical + Generative Engine Optimization (GEO/AEO) audit of any URL: measures TTFB, redirect chain, X-Robots-Tag, meta robots, canonical/hreflang, compression & security headers, title/meta/OpenGraph, H1-H3 question-heading density, structured lists/tables, empty CSR-shell detection, image alt coverage, E-E-A-T trust signals, composite geoScore (0-100), and ApexSEO Elite ICE action plan. Pair with ai_crawler_audit for site-wide robots.txt/llms.txt or geo_competitor_compare for rival benchmarking.

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": {
      "url": "<url>"
    },
    "name": "geo_page_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic HTTPS/HTTP URL to audit live (e.g. https://example.com).

Output Schema

NameRequiredDescriptionDefault
fetchNo
gradeYes
finalUrlYes
geoScoreYes
structureNo
subscoresYes
directivesNo
iceActionPlanYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare this as a safe, read-only, idempotent, open-world operation. The description adds useful behavioral context by specifying that the audit is live and enumerating many measured checks, including TTFB, redirects, headers, CSR-shell detection, alt coverage, and a composite score; it does not discuss latency, rate limits, or failure modes.

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?

The purpose is front-loaded, and the long audit checklist is dense but mostly earns its place by defining scope. Some phrases are jargon-heavy, such as 'ApexSEO Elite ICE action plan,' and the definition would be easier to scan if the checks were structured.

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?

For a one-parameter live audit tool with annotations and an output schema, the description is mostly complete: it explains what is audited and how it relates to key siblings. Return values need not be described because an output schema exists, though operational details such as timeouts or rate limits are absent.

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?

The single url parameter is fully documented in the schema with format and example. The description says 'any URL' but adds no further syntax, validation, or domain restrictions beyond the schema.

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?

The description states a specific verb and resource: it performs a live technical + GEO/AEO audit of a URL. It also makes the page-level scope clear by directing site-wide robots.txt/llms.txt checks to ai_crawler_audit and rival benchmarking to geo_competitor_compare.

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?

It gives explicit alternative-tool guidance: pair with ai_crawler_audit for site-wide crawler files or geo_competitor_compare for competitor benchmarking. It does not provide an explicit when-not-to-use statement, but the page-level versus site-wide distinction is clear.

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.