Google Search Console Audit MCP

Overview Schema Source Related Servers Discussions Admin

gsc_inspect_url

Read-onlyIdempotent

Inspect a single page's Google Search Console data: index status, mobile usability, rich results, and AMP. Diagnose why one URL isn't performing or appearing correctly.

Instructions

Full URL Inspection for one page: index, mobile, rich results and AMP.

Use this when one page needs a diagnosis. For an indexed-or-not sweep across many URLs use gsc_indexing_issues.

Quota: 600 inspections per minute and 2,000 per day, per property.

Input Schema

TableJSON Schema

Name	Required	Description
`no_cache`	No	Bypass the response cache for this call.
`page_url`	Yes	Fully qualified URL under site_url.
`site_url`	Yes	`sc-domain:example.com` for a domain property, or `https://example.com/` with the trailing slash for a URL-prefix property. Call gsc_sites if unsure.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`amp`	No
`verdict`	No
`page_url`	Yes
`site_url`	Yes
`index_status`	No
`rich_results`	No
`coverage_state`	No
`mobile_usability`	No
`inspection_result_link`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedv3.0.1Aug 28, 2026

addedInput schema / properties / no_cache

Added value: +{
+  "default": false,
+  "description": "Bypass the response cache for this call.",
+  "title": "No Cache",
+  "type": "boolean"
+}

addedInput schema / properties / page_url / description
```
Added value: +"Fully qualified URL under site_url."
```

addedInput schema / properties / site_url / description

Added value: +"`sc-domain:example.com` for a domain property, or `https://example.com/` with the trailing slash for a URL-prefix property. Call gsc_sites if unsure."

addedOutput schema / description

Added value: +"The URL Inspection payload for one page, with the sub-objects left as-is."

addedOutput schema / properties / amp

Added value: +{
+  "additionalProperties": true,
+  "title": "Amp",
+  "type": "object"
+}

addedOutput schema / properties / coverage_state

Added value: +{
+  "default": "",
+  "title": "Coverage State",
+  "type": "string"
+}

addedOutput schema / properties / index_status

Added value: +{
+  "additionalProperties": true,
+  "title": "Index Status",
+  "type": "object"
+}

addedOutput schema / properties / inspection_result_link

Added value: +{
+  "default": "",
+  "title": "Inspection Result Link",
+  "type": "string"
+}

addedOutput schema / properties / mobile_usability

Added value: +{
+  "additionalProperties": true,
+  "title": "Mobile Usability",
+  "type": "object"
+}

addedOutput schema / properties / page_url

Added value: +{
+  "title": "Page Url",
+  "type": "string"
+}

removedOutput schema / properties / result

Removed value: -{
-  "title": "Result",
-  "type": "string"
-}

addedOutput schema / properties / rich_results

Added value: +{
+  "additionalProperties": true,
+  "title": "Rich Results",
+  "type": "object"
+}

addedOutput schema / properties / site_url

Added value: +{
+  "title": "Site Url",
+  "type": "string"
+}

addedOutput schema / properties / verdict

Added value: +{
+  "default": "",
+  "title": "Verdict",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "result"
-]New value: +[
+  "site_url",
+  "page_url"
+]

changedOutput schema / title

Previous value: -"gsc_inspect_urlOutput"New value: +"InspectionResult"

First observedv2.0.2Apr 23, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds valuable rate-limit context (600/min and 2,000/day per property) and signals that a single URL is being inspected, extending beyond what annotations say without contradicting them.

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 description is three short, purposeful sentences: what it does, when to use it, and its quota. It is front-loaded with the core action and contains no filler. Every sentence earns its place.

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?

For a single-URL inspection tool with a complete input schema, rich annotations, and an output schema, the description covers the essential behavioral, quota, and sibling-selection context. Nothing needed to select or call the tool correctly is missing.

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 explains all parameters, including the site_url format and the no_cache option. The description does not add parameter-level detail beyond what is in the schema, so the baseline score of 3 is appropriate.

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?

The description opens with 'Full URL Inspection for one page' and enumerates the inspected dimensions: index, mobile, rich results, and AMP. It also names the sibling tool gsc_indexing_issues for the multi-URL sweep, making the tool's scope unambiguous. This clearly differentiates it from its siblings.

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?

The description states 'Use this when one page needs a diagnosis' and contrasts this with 'an indexed-or-not sweep across many URLs' pointing to gsc_indexing_issues. This gives the agent an explicit decision rule between the tool and its closest alternative.

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

Deploy Server