Google Search Console by Get MCP Ads

Overview Schema Source Related Servers Discussions Admin

gsc validate query

gsc_validate_query

Read-onlyIdempotent

Validates a Search Console metric, dimension, and search type combination before running a query, preventing invalid report requests.

Instructions

Validate a Search Console metric/dimension/search type combination before executing it.

Input Schema

Name	Required	Description	Default
`dateRange`	No	Explicit reporting start and end dates in YYYY-MM-DD format.
`dimensions`	No	Dimensions to validate.
`searchType`	No	Search surface to report, such as web, image, video, news or Discover. Availability depends on the property.	web

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.

Changed3 schema fields changedv2.1.1Oct 30, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / dateRange / 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

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds the useful nuance that the tool validates rather than executes, but it is silent on what a validation result looks like behaviorally (does an invalid combo raise an error or return a report?), and the presence of an output schema offsets the need to explain returns.

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?

A single front-loaded sentence with no filler; the purpose and the pre-execution timing are both stated immediately. It is perhaps too terse for the behavioral gaps it leaves, but as structure it is efficient.

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?

The tool is simple and both the schema and an output schema are rich, so the description does not need to carry much. Still, for a validation tool it leaves the key questions open: what is checked, whether invalid combinations return errors or warnings, and whether it is a required predecessor to the query tool.

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 all three parameters (dateRange, dimensions, searchType with enum) are documented in-schema, so the baseline of 3 applies. The description adds no format or constraint detail, and it mentions 'metric' as part of the validated combination even though no metric parameter exists — a small inconsistency that the schema silently corrects.

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 (validate) plus the resource concept (metric/dimension/search type combination), and the phrase 'before executing it' hints that this is a pre-flight check rather than a data-fetching call. It does not name the sibling it precedes (gsc_query_search_analytics), so sibling differentiation is implicit rather than explicit.

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?

'Before executing it' implies the usage window (pre-flight to an actual query), which is useful, but it never explicitly names gsc_query_search_analytics as the tool being validated for, nor does it say what to do when validation fails or whether this step is optional.

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