Skip to main content
Glama
mcp-google-gsc

mcp-google-gsc

by mharnett

gsc_inspection

Inspect a URL to verify Google Search indexing status and retrieve mobile usability and rich results data for diagnosing visibility issues.

Instructions

Inspect a URL to check if it is indexed in Google Search. Returns index status, mobile usability, and rich results data.

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": {
      "url": "<url>"
    },
    "name": "gsc_inspection"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe fully qualified URL to inspect (e.g., "https://www.example.com/blog/post")
site_urlNoSite URL / property (optional - auto-detected from config)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.2

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose that this is a read-only inspection and enumerates the returned data (index status, mobile usability, rich results). However, it omits meaningful behavioral constraints such as URL Inspection API quota limits, permission/verification requirements, and latency or failure modes.

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?

Two sentences, front-loaded with the action and the question it answers, followed by the return contents. No filler or restated name text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read tool with no output schema, the description usefully summarizes what comes back, which is the main gap-filler. It still leaves out operational constraints (quota, required access) that an agent would want before relying on it in a loop.

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 100%, and the schema already documents both the required fully-qualified URL and the optional site_url with auto-detection noted. 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ("Inspect a URL") plus the concrete question it answers ("check if it is indexed in Google Search"), which is far more informative than the bare tool name. It does not explicitly distinguish itself from siblings like gsc_search_analytics, but the purpose is unambiguous on its own.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer it should call this when it needs index status for a specific URL, but there is no explicit when-to-use statement, no mention of prerequisites (verified property, Search Console access), and no comparison to the analytics or site-listing siblings.

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