Skip to main content
Glama
Sign In
SEO Webmaster MCP

SEO Webmaster MCP

by JvnnDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

seo_audit_advanced

Read-onlyIdempotent

Audit a public URL's SEO by crawling pages and checking canonical, hreflang, headers, images, social metadata, and JSON-LD; returns evidence-backed prioritized actions.

Instructions

Audita una URL pública sin credenciales: rastreo, canonical, hreflang, encabezados, imágenes, metadatos sociales y propiedades JSON-LD seleccionadas. render=js activa un navegador instalado; performance=true consulta PageSpeed Insights. Propone acciones con evidencia y checks registra cobertura: cero acciones no implica revisión exhaustiva. Proveedores opcionales: Google Search Console y Bing. No guarda archivos.

Input Schema

NameRequiredDescriptionDefault
renderNojs usa Chrome/Chromium/Edge instalado; por defecto 10 páginas, máximo 20. static no inicia navegador.static
baseUrlYesURL completa que pertenece al sitio.
endDateNoFecha YYYY-MM-DD.
maxPagesNo
startDateNoFecha YYYY-MM-DD.
gscSiteUrlNoURL exacta de la propiedad verificada.
bingSiteUrlNoURL exacta de la propiedad verificada.
performanceNoConsulta PageSpeed Insights para la URL de entrada. Envía esa URL a Google; PAGESPEED_API_KEY opcional.
performanceStrategyNomobile

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.5.0
    • addedInput schema / properties / performance
      Added value: +{
+  "default": false,
+  "description": "Consulta PageSpeed Insights para la URL de entrada. Envía esa URL a Google; PAGESPEED_API_KEY opcional.",
+  "type": "boolean"
+}
    • addedInput schema / properties / performanceStrategy
      Added value: +{
+  "default": "mobile",
+  "enum": [
+    "mobile",
+    "desktop"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / render
      Added value: +{
+  "default": "static",
+  "description": "js usa Chrome/Chromium/Edge instalado; por defecto 10 páginas, máximo 20. static no inicia navegador.",
+  "enum": [
+    "static",
+    "js"
+  ],
+  "type": "string"
+}
  2. First observedv0.3.2

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, but the description adds context annotations cannot: no credentials required, js render spawns an installed browser, performance=true sends the target URL to Google (with optional PAGESPEED_API_KEY), and nothing is written to disk. The caveat that 'cero acciones no implica revisión exhaustiva' usefully frames how to read results.

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 audited surface, then the two behavior toggles, then the caveat and privacy note — a sensible order with dense, low-waste clauses. Minor duplication with the schema (render=js / performance=true are also described in the schema), but the sentences earn their place.

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?

For a 9-parameter tool with no output schema it covers the essentials: no auth, optional providers, no persistence, and a warning about result completeness. It does not explain why startDate/endDate exist (presumably scoping provider data) or point to the natural follow-on siblings seo_audit_save / seo_audit_report / seo_audit_history, which an agent needs to make the output useful.

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

Parameters4/5

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

Schema coverage is high (78%), so the baseline is 3, but the description adds real meaning for two of the nine parameters: render switches between static fetch and a real browser, and performance triggers an external PageSpeed call with an optional API key. date range, maxPages and the gsc/bing site URL parameters are only alluded to via 'Proveedores opcionales', leaving some schema documentation to carry them.

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?

States a specific verb+resource (audit a public URL) and enumerates exactly what is inspected: crawl, canonical, hreflang, headers, images, social metadata, JSON-LD. It never names the closest sibling (seo_audit_site) or the save/report siblings, so an agent must infer that this is the single-URL audit vs. a whole-site crawl. Clear purpose, but no explicit sibling differentiation.

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?

Gives concrete activation conditions for two options (render=js launches a browser; performance=true queries PageSpeed Insights) and states that no credentials are needed, with GSC/Bing as optional providers. It does not say when to prefer render=static vs js, when the extra PageSpeed call is warranted, or when to use seo_audit_site instead. Usage is implied rather than prescribed.

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