Skip to main content
Glama
SEO Audit MCP

SEO Audit MCP

by Nexariza-AI

Audit a web page

audit_page

Run a read-only technical SEO and AI-search readiness audit on one public URL, checking on-page elements, structured data, robots access, links and prioritized issues.

Instructions

Technical SEO and AI-search readiness audit of one public URL: title, meta description, headings, canonical, robots, Open Graph, JSON-LD structured data, images, links, word count and a prioritised issue list.

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": "audit_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe full URL to audit, e.g. https://example.com/pricing

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It conveys that this is a read-oriented audit and enumerates what is checked, but it does not disclose permissions, rate limits, error behavior for private or unreachable URLs, or whether the page is fetched live.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single front-loaded sentence that states the core purpose first and then lists the audit dimensions. The list is dense but every item helps the agent understand the scope of the audit.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description sufficiently explains what the audit covers for a one-parameter tool, but with no output schema it leaves the return structure only loosely described as a prioritised issue list. Operational details about URL accessibility and failure modes are also 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?

Schema coverage is 100%, so the parameter is already documented as a URI with an example. The description adds only the constraint that the URL should be public, which is useful but not a substantial expansion beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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: auditing one public URL for technical SEO and AI-search readiness. It clearly lists the audited elements, but it does not explicitly differentiate itself from siblings such as check_links or check_site_files.

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 comprehensive page-audit framing and the single public URL scope. However, there is no explicit when-to-use guidance, no exclusions, and no direction on when a narrower sibling tool would be preferable.

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