Skip to main content
Glama
Akxan

google-seo-mcp

by Akxan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Batch index coverage check

gsc_index_coverage
Read-onlyIdempotent

Diagnose indexing issues for batches of URLs or sitemap entries, retrieving coverage state, canonical mismatches, robots, last crawl, and rich-result problems.

Instructions

Use this for a batch; gsc_inspect_url returns the full raw result for a single URL. URL Inspection over a list of URLs or the first N sitemap URLs: verdict, coverage state, robots, last crawl, canonical mismatch, the sitemaps listing the URL, its referring URLs (first 5, referringUrlsTotal when more) and rich-result issues with severity. orphan=true means indexed but in no sitemap and with no known links to it; it is only set when the inspection came back complete, because Google omits both lists on partial results. One quota call (~2000/day) per URL, keep batches small.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlsNoExplicit URLs to inspect.
limitNoMax URLs when reading from the sitemap.
siteUrlYesSearch Console property, e.g. 'sc-domain:example.com' (see gsc_list_sites).
sitemapUrlNoAlternatively, take URLs from this sitemap (index supported).
languageCodeNoen-US
onlyProblemsNoReturn only URLs that are not indexed or have a canonical mismatch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.10.0
    • changedInput schema / properties / siteUrl / description
      Previous value: -"Search Console property, e.g. 'sc-domain:example.com' or 'https://example.com/' (see gsc_list_sites)."New value: +"Search Console property, e.g. 'sc-domain:example.com' (see gsc_list_sites)."
  2. Changed2 schema fields changedv0.5.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / siteUrl / description
      Previous value: -"Property URL exactly as shown in Search Console, e.g. 'https://example.com/' or 'sc-domain:example.com'. Use gsc_list_sites to discover it."New value: +"Search Console property, e.g. 'sc-domain:example.com' or 'https://example.com/' (see gsc_list_sites)."
  3. First observedv0.3.0

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 behavior that affects expectations: one quota call per URL, orphan=true semantics, and the caveat that orphan is only set on complete inspections because Google omits lists on partial results. This explains output nuances the annotations cannot convey.

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 compact and front-loads the key batch/single-URL decision. Every sentence adds distinct information: scope, output fields, orphan behavior, and quota constraints. There is no filler or repetition of schema content.

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?

With no output schema, the description enumerates the returned data (verdict, coverage state, robots, last crawl, canonical mismatch, sitemaps, referring URLs, rich-result issues) and flags operational constraints. An agent can anticipate both the response shape and the invocation size before calling.

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 coverage is 83%, so the schema already documents most parameters. The description adds context around 'first N sitemap URLs' and the batch-versus-single-URL distinction, but it does not add detail for languageCode or the precise filtering behavior of onlyProblems. This is adequate but not exceptional.

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 an explicit directive, 'Use this for a batch', identifies the resource as URL Inspection over a list of URLs or sitemap URLs, and enumerates the returned fields. It also distinguishes itself from the sibling gsc_inspect_url by stating that tool returns the full raw result for a single URL.

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?

It gives an explicit when-to-use rule ('for a batch') and names the alternative for single URLs (gsc_inspect_url). The quota warning ('~2000/day per URL, keep batches small') provides practical invocation guidance that helps the agent choose appropriate batch sizes.

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