Skip to main content
Glama
acamolese

Google Search Console Audit MCP

by acamolese
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

gsc_indexing_issues

Read-onlyIdempotent

Check whether a batch of URLs is indexed and get the reason for any that aren't. Returns a verdict per URL with indexing details.

Instructions

Check whether a batch of URLs is indexed, and why not when they are not.

Runs the inspections concurrently and returns one row per input URL, in input order. A URL that fails gets an error column instead of a verdict; the rest of the batch still comes back. For the full payload of a single page (mobile usability, rich results, AMP) use gsc_inspect_url.

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

Columns: url, verdict (PASS / PARTIAL / FAIL / NEUTRAL), coverage_state, robots_txt_state, indexing_state, page_fetch_state, crawled_as, last_crawl_time, google_canonical, user_canonical, error. The meta carries a verdict summary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pagesYesFully qualified URLs under site_url. At most 100 per call.
no_cacheNoBypass the response cache for this call.
site_urlYes`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.
response_formatNo`tsv` (default, compact) or `json`.tsv

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv3.0.1
    • 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 / pages / description
      Added value: +"Fully qualified URLs under site_url. At most 100 per call."
    • addedInput schema / properties / response_format
      Added value: +{
+  "default": "tsv",
+  "description": "`tsv` (default, compact) or `json`.",
+  "title": "Response Format",
+  "type": "string"
+}
    • 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."
  2. First observedv2.0.2

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses concurrency, one row per input URL in input order, per-URL error columns, partial batch results, quota limits, and the exact result columns. This is rich behavioral context an agent cannot infer from annotations alone.

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 well-structured and front-loaded: the core purpose appears in the first sentence, followed by behavioral details, alternative routing, quota, and output columns. Every sentence adds usable information without padding.

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?

The description covers purpose, behavior, error handling, quotas, output columns, and the relevant sibling tool. Combined with the thorough input schema and output schema, an agent has everything needed to select and invoke this tool correctly.

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?

The input schema already documents all four parameters with 100% coverage, so the baseline is 3. The description does not add parameter-level detail, but it does provide output-column context and quota constraints that indirectly help the agent understand what the parameters produce.

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 a specific verb and resource: 'Check whether a batch of URLs is indexed, and why not when they are not.' It clearly distinguishes this batch tool from the single-page alternative by naming gsc_inspect_url and contrasting batch rows versus full payload.

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 explicitly tells an agent when to use this tool versus gsc_inspect_url: for batch indexing checks versus full single-page payloads. This gives clear selection guidance without ambiguity.

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