Skip to main content
Glama
@mgcrea/mcp-google-search-console

@mgcrea/mcp-google-search-console

by mgcrea

Search Console: Inspect URL

gsc_inspect_url
Read-only

Inspect a URL's Google Search Console index status to diagnose coverage, canonical mismatches, robots.txt/noindex flags, last crawl results, and rich-result issues.

Instructions

Google's index status for one URL, as Search Console's URL Inspection reports it: verdict (PASS / NEUTRAL / FAIL), coverage state (e.g. "Crawled - currently not indexed"), robots.txt and noindex state, last crawl and fetch result, the canonical Google chose versus the one the page declares (canonical_mismatch is true when they differ), sitemaps and referring URLs it knows, and a rich-results summary. This is Google's indexed view, not a live test. QUOTA: 2,000 inspections per day and 600 per minute per property; for several URLs use gsc_inspect_urls.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site": "<site>",
      "url": "<url>"
    },
    "name": "gsc_inspect_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe page to inspect, as a full URL, e.g. "https://www.example.com/pricing". It must belong to `site`: for a URL-prefix property it starts with the property URL; for a domain property its host is the domain or a subdomain. Checked before any quota is spent.
siteYesThe Search Console property, e.g. "sc-domain:example.com" (a domain property: every protocol and subdomain) or "https://www.example.com/" (a URL-prefix property: exactly that scheme, host and path). A bare "example.com" or a URL without its trailing slash is resolved against the properties this account can see, preferring the domain property; the response's `site` says which property was read. gsc_list_sites lists them.
language_codeNoBCP-47 language for the issue messages, e.g. "en-US" or "fr". Defaults to English.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing concrete quota numbers (2,000/day, 600/minute per property) and by characterising data freshness — results are Google's indexed snapshot, not a live crawl. The only missing pieces are auth/setup behavior, which the sibling auth tools presumably cover.

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 core purpose, then the returned content, then the quota caveat and alternative — a sensible order. The middle sentence is a long comma-separated field list, which is dense but each item is informative; slight trimming of e.g. the quoted example coverage state would help.

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?

There is no output schema, so the field enumeration in the description is doing necessary work, and it covers the salient return values including the non-obvious canonical_mismatch boolean. Quota, scoping, and freshness caveats complete what an agent needs 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 description coverage is 100% and the schema already explains the site/url membership rule, property resolution, language default, and that validation happens before quota is spent. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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?

Names a specific verb and resource ('Google's index status for one URL ... as URL Inspection reports it') and enumerates the exact fields returned (verdict, coverage state, robots.txt/noindex, crawl and fetch info, canonicals, sitemaps, rich results). It also distinguishes itself from two lookalikes: the live-test tool behavior ('This is Google's indexed view, not a live test') and the batch sibling gsc_inspect_urls.

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?

Explicitly routes multi-URL use to gsc_inspect_urls and warns that this tool reflects the indexed view rather than a live fetch, which is the main misuse trap for URL inspection. The alternative and the condition that selects it are stated rather than inferred.

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