Skip to main content
Glama
Mehmoodqureshi

seo-mcp

by Mehmoodqureshi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

audit_page

Run an on-page SEO audit for a URL, checking title, meta, indexability, redirects, headings, links, images, and structured data, then return issues and a 0–100 score.

Instructions

Full on-page SEO audit of a URL: title, meta description, canonical, indexability (meta robots, X-Robots-Tag header, and robots.txt), redirect chain, viewport, Open Graph/Twitter, heading outline and hierarchy, word count, image alt coverage, internal/external link counts, structured-data presence, plus a list of issues and a 0–100 score. Free, no API key. Set pagespeed=true to also attach PageSpeed Insights performance metrics. After presenting the results, ASK THE USER whether they want a professionally formatted PDF report; if they say yes, call export_audit_pdf with the same url (and same pagespeed/strategy).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesPage URL (https:// optional)
localNoWhen pagespeed=true, force the local Lighthouse engine instead of Google PSI (no API key/quota; requires Chrome installed). Default false — PSI is used first and falls back to local automatically when it is over quota.
detailNoWhen pagespeed=true, also attach the full GTmetrix-style detail layer under pagespeed.detail (all category scores, diagnostics, resource breakdown, suggestions, passed checks). Default false.
strategyNoPageSpeed strategy when pagespeed=true: "mobile" (default) or "desktop"
pagespeedNoAlso run PageSpeed Insights and attach performance metrics (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.9
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / detail
      Added value: +{
+  "description": "When pagespeed=true, also attach the full GTmetrix-style detail layer under pagespeed.detail (all category scores, diagnostics, resource breakdown, suggestions, passed checks). Default false.",
+  "type": "boolean"
+}
    • addedInput schema / properties / local
      Added value: +{
+  "description": "When pagespeed=true, force the local Lighthouse engine instead of Google PSI (no API key/quota; requires Chrome installed). Default false — PSI is used first and falls back to local automatically when it is over quota.",
+  "type": "boolean"
+}
    • addedInput schema / properties / strategy / enum
      Added value: +[
+  "mobile",
+  "desktop"
+]
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it enumerates the full returned payload, notes the no-API-key/free constraint, and explains that pagespeed=true attaches PSI metrics with a local-engine fallback. It stops short of documenting error/rate-limit behavior or how the URL is fetched, so it is strong but not exhaustive.

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-loads the purpose and keeps the critical workflow instruction (ask the user, then call export_audit_pdf) as the final sentence. The long enumerative middle sentence is dense but each listed check conveys real capability, so waste is minimal.

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?

No output schema or annotations exist, yet the description fully describes the return contents, the free/no-key constraint, the optional performance layer, and the downstream PDF handoff. An agent has everything needed to call it and to act on the result.

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%, so the schema already documents all five parameters, including local/detail/strategy. The description only reinforces the pagespeed flag and carries it forward into the PDF step ('same pagespeed/strategy'), adding workflow meaning but no syntax beyond the schema — 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+resource ('Full on-page SEO audit of a URL') and enumerates exactly what is checked (title, meta, canonical, indexability, redirect chain, headings, links, structured data, issues, score). This clearly separates it from siblings like audit_site (site-level), pagespeed (performance-only), and check_robots (single concern).

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?

Gives clear operating context ('Free, no API key'), explains the pagespeed=true option to add PSI metrics, and prescribes a concrete follow-up workflow with export_audit_pdf. It does not, however, state when to prefer this over the sibling pagespeed tool or audit_site for whole-site scans, so exclusions are missing.

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