Google Search Console MCP Server

Overview Schema Source Related Servers Discussions Admin

Compare Periods

compare_periods

Compare a period against the equal-length period immediately before it to reveal changes in Google Search Console performance.

Instructions

Compare a period against the equal-length period immediately before it.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`filters`	No	Simplified filters combined with AND.
`end_date`	No	Inclusive end of the current period.
`site_url`	Yes	Property identifier.
`dimension`	No	Optional dimension to break the comparison down by, e.g. QUERY or PAGE. Omit for property-level totals only.
`row_limit`	No	Rows per period when a dimension is given.
`start_date`	No	Inclusive start of the current period. Defaults to a 28-day window ending three days ago.
`search_type`	No	Report type.	WEB

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 14, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose whether the operation is read-only, what permissions are required, whether there are rate limits, or how pagination works.

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?

It is a single front-loaded sentence with zero waste. The comparison semantics are stated immediately.

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 schema fully documents parameters and an output schema exists, so the description need not cover returns. Still, it omits when-to-use guidance and behavioral context, leaving it only minimally complete for an analytics comparison 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%, so the parameter meanings are already fully documented in the schema. The description adds no parameter-level meaning beyond what is structured.

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: compare a period against the equal-length period immediately before it. However, it does not distinguish this tool from sibling analytics tools such as performance_by_date or query_search_analytics.

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?

No when-to-use guidance, prerequisites, or alternatives are given. The description only says what the tool does, leaving the agent to infer when it should be selected over siblings.

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