Google Search Console by Get MCP Ads

Overview Schema Source Related Servers Discussions Admin

gsc bulk inspect urls

gsc_bulk_inspect_urls

Read-onlyIdempotent

Inspect up to 10 URLs at once in Google Search Console, returning normalized results and per-URL errors while protecting URL Inspection quota.

Instructions

Inspect multiple URLs with a conservative sequential limit and normalized URL Inspection results. Quota: 2000 requests/day/property.

Input Schema

Name	Required	Description
`urls`	Yes	Full URLs to inspect. Maximum 10 per call to protect URL Inspection quota.
`siteUrl`	No	Search Console property URL, e.g. https://example.com/ or sc-domain:example.com. Uses GSC_SITE_URL when omitted.
`languageCode`	No	Optional IETF language tag, e.g. en-US or fr-FR.
`continueOnError`	No	When true, returns per-URL errors instead of failing the entire batch.

Output Schema

Name	Required	Description	Default
`result`	Yes	Original tool result: parsed JSON when the text is JSON, otherwise the text or multiple MCP content blocks. Provider fields depend on the selected query.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.1.1Oct 30, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / properties / result / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  },
-  {
-    "items": {},
-    "type": "array"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  {
+    "items": {},
+    "type": "array"
+  },
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

First observedv2.0.1Sep 23, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description correctly adds context they cannot: sequential conservative execution, normalized output, and the 2000 requests/day/property quota. It stops short of stating what normalization means or how partial failures surface (though continueOnError in the schema covers that).

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, zero waste: behavioral scope first, hard quota constraint second. Nothing to trim and the constraint is front-loaded.

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

Completeness4/5

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

With an output schema, complete parameter descriptions, and safety annotations, the description only needs to carry quota and execution behavior, which it does. Slightly incomplete on how errors are aggregated, though continueOnError's schema description covers that ground.

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%, so all four parameters (urls, siteUrl, languageCode, continueOnError) are already documented in the schema. The description adds only the quota rationale, which partially overlaps the urls maxItems note, so baseline 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?

States a specific verb and resource ('Inspect multiple URLs') and the batching scope, which inherently separates it from the single-URL sibling gsc_inspect_url. It does not name that sibling explicitly, so differentiation is implied rather than stated.

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?

The word 'multiple' and the 10-URL cap imply batch usage, but the description never says when to prefer this over gsc_inspect_url or gsc_plan_large_site_sampling, nor when not to use it. Usage is inferable only from the tool name and quota note.

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