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

@mgcrea/mcp-google-search-console

by mgcrea

Search Console: Inspect URLs

gsc_inspect_urls
Read-only

Batch inspect up to 20 URLs at once to check indexing, canonical mismatches, and rich results, returning per-URL verdicts, errors, and a quota-use summary.

Instructions

Inspect up to 20 URLs of one property, 3 at a time, with the same per-URL fields as gsc_inspect_url plus a summary (verdicts, canonical mismatches). Prefer this over calling gsc_inspect_url repeatedly — but each URL still costs one of the property's 2,000 daily inspections; quota_used estimates how many were spent. A URL that fails comes back with its own error and remedy instead of failing the call; on a quota, permission or sign-in error the remaining URLs are skipped rather than burned.

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>",
      "urls": "<urls>"
    },
    "name": "gsc_inspect_urls"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
urlsYes1-20 full URLs inside `site`, e.g. ["https://www.example.com/a", "https://www.example.com/b"]. Duplicates are inspected once.
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.7/5.0
Behavior4/5

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

Well beyond the readOnly/openWorld annotations: it discloses the concurrency limit (3 at a time), the per-URL quota cost and daily cap, the `quota_used` estimate, and the failure model — per-URL `error`/`remedy` instead of a failed call, with remaining URLs skipped on quota, permission or sign-in errors. It stops short of describing output ordering or whether partial results are returned alongside a top-level error, but the operational profile is unusually complete.

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?

A single tight paragraph, front-loaded with what the tool does and what it returns, then the alternative, then quota and failure behavior. Every sentence carries distinct information; nothing restates the schema or the annotations.

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 carries the return-value burden and does so: per-URL fields mirroring gsc_inspect_url, a summary with verdicts and canonical mismatches, and a documented per-URL error/remedy shape. For a 3-parameter batched read tool this leaves nothing an agent needs 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, and the description adds real meaning on top: each element of `urls` consumes a quota unit and `quota_used` estimates the spend, which directly informs how many URLs to pass. `site` and `language_code` are fully specified in the schema and need no restatement here.

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?

States a specific verb and resource ('Inspect up to 20 URLs of one property'), the batch shape ('3 at a time'), and how its output relates to the sibling ('the same per-URL fields as gsc_inspect_url plus a summary'). An agent can distinguish it from gsc_inspect_url without opening either schema.

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?

Gives an explicit routing rule: 'Prefer this over calling gsc_inspect_url repeatedly', naming the alternative and the condition that selects it. It also surfaces the cost tradeoff (each URL still costs one of the property's 2,000 daily inspections) so the agent can weigh batching against quota.

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