Skip to main content
Glama
Sign In
geoseo-mcp

geoseo-mcp

by Rachit8484
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

audit_page

Audit a single page for SEO and GEO readiness, including title, meta, headings, schema, and score. Flags pages that are empty without JavaScript to ensure AI crawlers can read them.

Instructions

Audit a single page (local file path or http(s) URL).

Set render=True to audit the page after JavaScript runs (needs the optional geoseo-mcp[render] extra + playwright install chromium). Either way the report flags pages that are empty without JavaScript, since most AI crawlers don't execute it.

Returns a structured report with: title/meta/headings, word count, link counts, image alt coverage, JSON-LD schema types, Open Graph, Twitter Card, freshness signals, GEO-quotability score, and a list of human-readable findings. Plus a 0-100 overall score.

Examples: audit_page("seo/aa-meetings-what-to-expect.html") audit_page("https://soberpath.com/blog/quit-drinking")

Input Schema

NameRequiredDescriptionDefault
renderNo
sourceYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.0
    • addedInput schema / properties / render
      Added value: +{
+  "default": false,
+  "type": "boolean"
+}
  2. First observedv0.3.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does a good job: it discloses the optional render path, its extra dependency, the fact that non-JS rendering is flagged, and the shape of the returned report plus score. It stops short of stating explicitly that the tool is read-only or whether network access/auth is involved.

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 definition is front-loaded with the core purpose, followed by the render caveat, return summary, and examples. The return-value enumeration is somewhat lengthy given that an output schema exists, which keeps it from being maximally tight.

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 two-parameter audit tool with an output schema, the description supplies the critical operational detail: input forms, render behavior and dependency, and the presence of an overall score and findings. Only an explicit statement of read-only behavior or side-effect profile is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does: source is described as a local file path or http(s) URL, and render is explained as running the page after JavaScript with a named installation prerequisite. Concrete example calls further pin down the expected argument format.

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 first line states a specific verb and resource ('Audit a single page') and immediately distinguishes the accepted input forms (local file path or http(s) URL). The single-page scope also separates it from the sibling audit_site tool without ambiguity.

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 clearly establishes the single-page context and explains when to set render=True, including the prerequisite extra and playwright install. It does not explicitly name audit_site as the alternative for whole-site auditing, so the routing guidance is clear but not complete.

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

Deploy Server

Other Tools