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 periods for query or page performance to identify clicks, impressions, CTR, and position changes. Pinpoint losses and gains for informed SEO decisions.

Instructions

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

Input Schema

TableJSON 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

TableJSON 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.

First observedv2.0.1Sep 23, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare the tool read-only, idempotent, and non-destructive. The description adds that it compares two periods and returns deltas for four metrics, which is useful but not extensive; it does not explain ranking behavior, period defaults, or filtering semantics, leaving much of the behavioral context to the schema and output schema.

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, front-loaded sentence communicates the core operation, scope, and return values without any filler. Every word earns its place, and the structure makes the tool's purpose immediately scannable.

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?

For a tool with 10 parameters, nested date-range objects, and an output schema, the description is brief but the surrounding structured information is rich and complete. The main missing piece is explicit routing guidance among the many related GSC siblings, which prevents a 5.

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 the baseline is 3 even without additional parameter explanation in the description. The description does map loosely to the 'dimension' and 'sortBy' concepts by mentioning query/page and metric deltas, but it adds no new parameter-level meaning beyond what the schema already provides.

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 states a specific action ('Compare two periods'), a clear resource scope ('query or page performance'), and the exact output metrics ('click/impression/CTR/position deltas'). This distinguishes it from siblings like gsc_query_search_analytics, which targets single-period queries, and gsc_compare_search_types, which compares search types rather than periods.

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 description implies the primary use case: when an agent needs period-over-period performance comparison. However, it does not explicitly state when to avoid this tool or name alternatives such as gsc_query_search_analytics for single-period reporting, so the usage guidance remains implicit rather than explicit.

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