SEO GSC Wizard MCP

On-page SEO audit

audit_onpage_seo

Read-only

Use this when the user asks for a technical or on-page SEO check of specific pages or of the top pages. Crawls a property's pages and runs a technical on-page/SEO audit per URL: HTTP status, indexability (noindex / canonicalised), title & meta-description length, H1s, word count, canonical, internal/external links, image alt coverage, structured data, Open Graph, viewport, hreflang, and a scored list of issues by severity. Pages come back worst first: by issueCount, then impressions. Pass explicit urls, or omit them to audit the top pages by Search Console impressions. URLs must belong to the property. Fetches each page live and stops after about 50 seconds: when truncated is true, the pages in notAudited were not fetched, so call again with urls set to that list to finish. Not for whether Google indexed a URL: use inspect_url.

Input Schema

Name	Required	Description
`urls`	No	Explicit page URLs to audit (max 25). Omit to auto-pick top pages.
`maxUrls`	No	How many pages to audit when auto-picking (default 10, max 25).
`siteUrl`	Yes
`minImpressions`	No	When auto-picking, only consider pages with at least this many impressions (28-day).

Output Schema

Name	Required	Description
`pages`	No
`thenBy`	No
`listKey`	No	Name of the top-level field that holds the rows sortedBy describes.
`message`	No
`siteUrl`	No
`skipped`	No
`summary`	No
`nextStep`	No
`ordering`	No
`sortedBy`	No
`crawlNote`	No
`sortOrder`	No
`thenOrder`	No
`truncated`	No
`budgetNote`	No
`dataSource`	No
`notAudited`	No
`robotsNote`	No
`contextNote`	No
`auditedCount`	No
`contextRange`	No
`emptyBecause`	No
`methodLimits`	No
`metricsUnavailable`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

addedOutput schema / properties / listKey

Added value: +{
+  "$ref": "#/properties/siteUrl",
+  "description": "Name of the top-level field that holds the rows sortedBy describes."
+}

Changed13 schema fields changedOct 18, 2026

changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +true
```

changedOutput schema / properties / contextRange / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "days": {
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "endDate": {
-        "$ref": "#/properties/siteUrl"
-      },
-      "startDate": {
-        "$ref": "#/properties/siteUrl"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "days": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "endDate": {
+        "$ref": "#/properties/siteUrl"
+      },
+      "startDate": {
+        "$ref": "#/properties/siteUrl"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / emptyBecause

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

addedOutput schema / properties / methodLimits

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

addedOutput schema / properties / metricsUnavailable

Added value: +{
+  "$ref": "#/properties/truncated"
+}

addedOutput schema / properties / nextStep

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

addedOutput schema / properties / ordering

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {
+        "additionalProperties": true,
+        "properties": {
+          "sortOrder": {
+            "$ref": "#/properties/siteUrl"
+          },
+          "sortedBy": {
+            "$ref": "#/properties/siteUrl"
+          },
+          "thenBy": {
+            "$ref": "#/properties/siteUrl"
+          },
+          "thenOrder": {
+            "$ref": "#/properties/siteUrl"
+          }
+        },
+        "type": "object"
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / properties / skipped / items / additionalProperties
```
Previous value: -falseNew value: +true
```

addedOutput schema / properties / sortOrder

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

addedOutput schema / properties / sortedBy

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

changedOutput schema / properties / summary / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "by_severity": {},
-      "indexable_pages": {
-        "$ref": "#/properties/contextRange/anyOf/0/properties/days"
-      },
-      "non_indexable_pages": {
-        "$ref": "#/properties/contextRange/anyOf/0/properties/days"
-      },
-      "total_issues": {
-        "$ref": "#/properties/contextRange/anyOf/0/properties/days"
-      },
-      "total_pages": {
-        "$ref": "#/properties/contextRange/anyOf/0/properties/days"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "by_severity": {},
+      "indexable_pages": {
+        "$ref": "#/properties/contextRange/anyOf/0/properties/days"
+      },
+      "non_indexable_pages": {
+        "$ref": "#/properties/contextRange/anyOf/0/properties/days"
+      },
+      "total_issues": {
+        "$ref": "#/properties/contextRange/anyOf/0/properties/days"
+      },
+      "total_pages": {
+        "$ref": "#/properties/contextRange/anyOf/0/properties/days"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / thenBy

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

addedOutput schema / properties / thenOrder

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

Changed4 schema fields changedOct 10, 2026

addedOutput schema / properties / budgetNote

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

addedOutput schema / properties / contextNote

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

addedOutput schema / properties / notAudited

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / truncated

Added value: +{
+  "type": [
+    "boolean",
+    "null"
+  ]
+}

First observedOct 7, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the readOnly/openWorld annotations, it discloses real operational behavior: pages are fetched live, the run stops after ~50 seconds, and truncated=true means the URLs in notAudited still need a follow-up call. It also states result ordering (issueCount, then impressions) and the constraint that URLs must belong to the property — none of which the annotations convey.

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-loaded with the trigger and purpose, then scope, then pagination/continuation semantics, then the sibling exclusion — a sensible order. The single long enumeration of audited checks is dense but earns its place by telling the agent what the report will contain.

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?

An output schema exists, so return values need not be described; instead the description covers what the agent can't infer — ordering, truncation, and the continuation pattern. For a live-crawl tool with a time budget, that is the hard part and it is handled.

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 75%, and the description adds meaning the schema does not: URLs must belong to the property, top pages are picked by Search Console impressions, and notAudited can be fed back into `urls` for a continuation run. The maxUrls/minImpressions auto-pick knobs are left to the schema, which documents them adequately.

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?

Specific verb + resource (“runs a technical on-page/SEO audit per URL”) with an enumerated scope of what's checked. It explicitly distinguishes itself from inspect_url, which is the nearest sibling, so an agent can separate the two without consulting either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Opens with the triggering condition (“Use this when the user asks for a technical or on-page SEO check of specific pages or of the top pages”) and closes with an explicit exclusion plus the named alternative: “Not for whether Google indexed a URL: use inspect_url.” Both when-to-use and when-not-to-use are stated.

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

All SEO GSC Wizard MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?