Skip to main content
Glama
Mehmoodqureshi

seo-mcp

by Mehmoodqureshi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

export_audit_pdf

Generate a PDF report of an on-page SEO audit for any URL. Re-run the audit, include score, issues, metadata, and optional PageSpeed metrics, then save the file and return its path.

Instructions

Generate a professionally laid-out PDF report of an on-page SEO audit (score badge, summary cards, severity-colored issue list, metadata, content/structure, social tags, and optional PageSpeed metrics). Re-runs the audit for the URL and writes a .pdf to disk, returning the file path. Use this after audit_page when the user asks for a PDF report.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesPage URL to audit and export (https:// optional)
pathNoOutput file path (default: ./seo-audit-<host>-<date>.pdf in the current directory). ".pdf" is appended if missing.
detailNoInclude the full GTmetrix-style detail in the PDF (category scores, diagnostics, resource weight, prioritized suggestions, passed checks). Defaults to true when pagespeed=true.
strategyNoLimit the PageSpeed section to one strategy: "mobile" or "desktop". Omit to include BOTH in the same file (default).
pagespeedNoAlso run PageSpeed and include performance metrics in the report (default false). When true, BOTH Mobile and Desktop are included in the same PDF unless a single "strategy" is specified.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.9
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / detail
      Added value: +{
+  "description": "Include the full GTmetrix-style detail in the PDF (category scores, diagnostics, resource weight, prioritized suggestions, passed checks). Defaults to true when pagespeed=true.",
+  "type": "boolean"
+}
    • changedInput schema / properties / pagespeed / description
      Previous value: -"Also run PageSpeed Insights and include performance metrics in the report (default false)"New value: +"Also run PageSpeed and include performance metrics in the report (default false). When true, BOTH Mobile and Desktop are included in the same PDF unless a single \"strategy\" is specified."
    • changedInput schema / properties / strategy / description
      Previous value: -"PageSpeed strategy when pagespeed=true: \"mobile\" (default) or \"desktop\""New value: +"Limit the PageSpeed section to one strategy: \"mobile\" or \"desktop\". Omit to include BOTH in the same file (default)."
    • addedInput schema / properties / strategy / enum
      Added value: +[
+  "mobile",
+  "desktop"
+]
  2. First observedv0.1.0

TDQS

A4.1/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 disclose the key side effects: it re-runs the audit (fresh network work) and writes a .pdf to disk, returning the file path. It omits overwrite behavior, latency expectations, and failure modes, which keeps it short of a 5.

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?

Purpose is front-loaded in the first clause, followed by side effects and then usage, so the agent can stop reading early. The parenthetical inventory of report sections is long but earns its place by telling the agent what the artifact contains.

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?

No output schema exists, but the description states the return value (file path) and the write-to-disk behavior, and all five parameters are covered by the schema. A note on whether an existing file is overwritten would close the remaining gap.

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 every parameter (url, path, detail, strategy, pagespeed) is already documented, and the enum on strategy is self-explanatory. The description adds report-content context that loosely maps to pagespeed/detail but no format or constraint detail beyond the schema, so 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 (Generate) and resource (PDF report of an on-page SEO audit) and enumerates the report contents, so the agent knows exactly what artifact comes back. It also distinguishes scope from the sibling export_site_pdf by tying itself to a single URL audit.Page

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?

"Use this after audit_page when the user asks for a PDF report" gives an explicit precondition and trigger. It does not, however, draw an exclusion against the sibling export_site_pdf, leaving the single-page vs site-wide routing to inference.

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