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

@mgcrea/mcp-google-search-console

by mgcrea

Search Console: Request

gsc_request
Read-only

Calls a Search Console API endpoint that lacks a dedicated tool, returning raw GET responses for sites, sitemaps, or URL inspection paths.

Instructions

Escape hatch: call a Search Console API endpoint that has no dedicated tool. The path must be under /webmasters/v3/ (sites, sitemaps, searchAnalytics) or /v1/urlInspection/, with the property URL-encoded as one segment, e.g. GET /webmasters/v3/sites/sc-domain%3Aexample.com. Returns the raw response, unshaped — prefer the dedicated tools, which resolve the property and name the fields. Writes are DISABLED: only GET is permitted, so the POST-only search analytics and URL inspection endpoints are reachable only through their dedicated tools. Set GSC_ALLOW_WRITES=1 to allow other methods.

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": {
      "path": "<path>"
    },
    "name": "gsc_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoJSON body for POST/PUT.
pathYesPath on searchconsole.googleapis.com, e.g. "/webmasters/v3/sites" or "/webmasters/v3/sites/https%3A%2F%2Fwww.example.com%2F/sitemaps".
queryNoQuery parameters, e.g. {"sitemapIndex": "https://www.example.com/sitemap.xml"}.
methodNoHTTP method.GET

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description stays consistent while adding context the annotations cannot express: the response is returned raw and unshaped, only GET is permitted, POST-only endpoints are therefore unreachable here, and an environment variable overrides the restriction. That is exactly the extra behavioral surface an agent needs for a passthrough tool.

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?

Six tight sentences, front-loaded with the tool's role, then constraints, then the write restriction. Each sentence carries distinct information — no restatement of the name, no filler — and the most decision-relevant fact (prefer dedicated tools) appears early.

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 raw API passthrough with an open-world annotation and no output schema, the description covers the allowed path space, encoding rule, method restriction, override flag, and the fact that responses are unshaped. Nothing an agent needs in order to invoke it safely is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns an extra point by constraining `path` to /webmasters/v3/ or /v1/urlInspection/ and requiring the property to be URL-encoded as a single segment. It does not, however, say anything about `body` or `query` beyond what the schema already documents.

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 concrete noun phrase — "Escape hatch: call a Search Console API endpoint that has no dedicated tool" — which states the verb (call an arbitrary endpoint), the resource (Search Console API), and its exact niche relative to the dedicated siblings. An agent can tell immediately whether this is the right tool or whether gsc_query_search_analytics / gsc_inspect_url should be used instead.

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 names the when (endpoint has no dedicated tool), the when-not ("prefer the dedicated tools, which resolve the property and name the fields"), and the hard constraint that writes are disabled via GET-only plus the GSC_ALLOW_WRITES=1 escape. This is about as explicit as routing guidance gets.

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