gsc-mcp-server

Overview Schema Source Related Servers Discussions Admin

compare_search_periods

Compare search analytics data between two date ranges to identify changes in queries, pages, and performance. Pinpoint ranking shifts and traffic trends in Google Search Console.

Instructions

Compare search analytics data between two time periods.

Args:
    site_url: Exact GSC property URL from list_properties (e.g. "https://example.com/" or
              "sc-domain:example.com"). Domain properties cover all subdomains — use the
              domain property as site_url and filter by page to analyze a specific subdomain.
    period1_start: Start date for period 1 (YYYY-MM-DD)
    period1_end: End date for period 1 (YYYY-MM-DD)
    period2_start: Start date for period 2 (YYYY-MM-DD)
    period2_end: End date for period 2 (YYYY-MM-DD)
    dimensions: Dimensions to group by (default: query)
    limit: Number of top results to compare (default: 10)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site_url": "<site_url>",
      "period1_start": "<period1_start>",
      "period1_end": "<period1_end>",
      "period2_start": "<period2_start>",
      "period2_end": "<period2_end>"
    },
    "name": "compare_search_periods"
  }
}

Input Schema

Name	Required	Default
`limit`	No
`site_url`	Yes
`dimensions`	No	query
`period1_end`	Yes
`period2_end`	Yes
`period1_start`	Yes
`period2_start`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.3Aug 13, 2026

TDQS

A4.1/5.0

Behavior3/5

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

With no annotations, the description carries the burden for behavioral context. It adds a useful GSC-related behavior ('Domain properties cover all subdomains') and explains how to adapt site_url plus page filtering for subdomains. Still, it does not disclose permissions, read-only/side-effect status, rate limits, or how 'top results' are ranked, leaving behavioral transparency only partially covered.

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?

The one-line purpose is front-loaded, followed by a tight Args list. Every line earns its place: formats, defaults, and the domain-property guidance are all necessary for correct invocation. There is no filler or repetition.

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?

The description covers all seven parameters, includes the key domain-vs-site property nuance, and the presence of an output schema covers return-value details. It is slightly incomplete because dimensions has no allowed-value list ('query', 'page', etc.) and 'top results' does not specify the ranking metric, but these are minor gaps for an otherwise well-specified tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description compensates fully: site_url includes exact expected formats and examples, all four date parameters specify YYYY-MM-DD, and dimensions/limit explain their defaults and purpose. This adds substantial meaning beyond the bare schema titles.

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 starts with a specific verb and resource: 'Compare search analytics data between two time periods.' This unambiguously names the tool's operation and distinguishes it from single-period siblings like get_search_analytics, so an agent can select it without opening the schema.

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 intended use case (comparing two periods) is clear, and the site_url note correctly ties the parameter to list_properties. However, the description never explicitly says when to prefer this tool over get_search_analytics or get_advanced_search_analytics, nor states exclusions such as 'use for single-period trends instead.' The usage guidance is implied rather than stated.

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