Google Search Console by Get MCP Ads

Overview Schema Source Related Servers Discussions Admin

gsc find losses gains

gsc_find_losses_gains

Read-onlyIdempotent

Compare two date ranges for query or page performance to identify losses and gains in clicks, impressions, CTR, and position, returning ranked metric deltas.

Instructions

Compare two periods for query or page performance and return click/impression/CTR/position deltas.

Input Schema

Name	Required	Description	Default
`topN`	No	Maximum number of highest-ranked results to return.
`limit`	No	Rows to fetch for each period.
`sortBy`	No	Metric or dimension used to rank the returned results.	clicksDelta
`siteUrl`	No	Search Console property URL, e.g. https://example.com/ or sc-domain:example.com. Uses GSC_SITE_URL when omitted.
`dimension`	No	Reporting dimension used to group and compare results.	query
`datePreset`	No	Named reporting period. Use the custom date range when you need exact start and end dates.	last28days
`searchType`	No	Search surface to report, such as web, image, video, news or Discover. Availability depends on the property.	web
`currentDateRange`	No	Current period. Defaults to datePreset.
`minAbsClickDelta`	No	Filter out rows with smaller absolute click delta.
`previousDateRange`	No	Previous period. Defaults to the immediately preceding period with the same length.

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.

Changed7 schema fields changedv2.1.1Oct 30, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / currentDateRange / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / previousDateRange / $ref
```
Removed value: -"#/properties/currentDateRange"
```

addedInput schema / properties / previousDateRange / properties

Added value: +{
+  "endDate": {
+    "description": "End date YYYY-MM-DD",
+    "type": "string"
+  },
+  "startDate": {
+    "description": "Start date YYYY-MM-DD",
+    "type": "string"
+  }
+}

addedInput schema / properties / previousDateRange / required
```
Added value: +[
+  "startDate",
+  "endDate"
+]
```
addedInput schema / properties / previousDateRange / type
```
Added value: +"object"
```

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.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds that the tool returns deltas rather than raw rows, which is useful, but it says nothing about cost/latency of fetching two periods, topN/limit interaction, or how previousDateRange is defaulted.

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?

One sentence, front-loaded with the comparison action and the returned metrics, with no filler. It is efficient, though the brevity leaves important behavioral details unstated.

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

Completeness2/5

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

This is a complex tool: 10 parameters, nested current/previous date range objects, a preset fallback, and topN vs limit semantics. Given that surface, a single sentence does not tell the agent how the two periods are constructed, what the previous-period default means, or how ranking/filtering interact, leaving meaningful gaps despite the presence of an output schema and strong annotations.

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 each of the 10 parameters (including nested date-range objects) is documented in the schema. The description contributes no additional parameter meaning, 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?

States a specific verb ('Compare') and resource ('query or page performance') and names the exact outputs ('click/impression/CTR/position deltas'). It is clear enough to distinguish from gsc_query_search_analytics, but it never explicitly contrasts itself with siblings like gsc_compare_search_types, so it stops short of a 5.

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

Usage Guidelines2/5

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

The only guidance is the implicit 'use this to compare two periods'. There is no statement of when to prefer it over gsc_query_search_analytics or gsc_compare_search_types, no mention of prerequisites, and no hint about how to choose between datePreset and the custom range objects.

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