Skip to main content
Glama

search_console_analytics_compare_periods

Compare Search Console analytics across two time periods side-by-side. Returns clicks, impressions, CTR, and position for each period under shared dimensions like query or page.

Instructions

Query Search Console search analytics twice and return both periods side-by-side. Returns {period_1: [rows], period_2: [rows]} where each rows list has the same shape as search_console_analytics_query (keys, clicks, impressions, ctr, position). The tool does NOT diff or merge the periods — the agent must align by the first key in each row. Read-only. Two REST calls are issued per invocation. Defaults: dimensions=['query'], row_limit=100 per period. For a single-period query use search_console_analytics_query.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
site_urlYesProperty identifier as registered in Search Console. For URL-prefix properties use the full URL including trailing slash (e.g. 'https://example.com/'). For Domain properties use the 'sc-domain:' prefix (e.g. 'sc-domain:example.com'). The property must be verified and accessible to the authenticated Google account.
start_date_1YesPeriod 1 inclusive start date ('YYYY-MM-DD'). Convention: period 1 is the older / baseline window.
end_date_1YesPeriod 1 inclusive end date ('YYYY-MM-DD'). Must be >= start_date_1.
start_date_2YesPeriod 2 inclusive start date ('YYYY-MM-DD'). Convention: period 2 is the newer / comparison window.
end_date_2YesPeriod 2 inclusive end date ('YYYY-MM-DD'). Must be >= start_date_2.
dimensionsNoDimensions shared across both periods. Default ['query']. Use ['page'] to compare URL-level changes, ['device'] for device shifts.
row_limitNoMaximum rows per period (default 100, cap 25000). Applied independently to period 1 and period 2.
Behavior5/5

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

Discloses read-only nature, that two REST calls are made per invocation, and the return format. Clearly states what the tool does NOT do (no diff/merge), which is crucial for correct agent behavior.

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?

5 concise sentences covering purpose, return shape, limitations, read-only + call count, and alternative. No redundant information, front-loaded with most important details.

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

Completeness5/5

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

For a two-period comparison tool with 7 parameters, the description fully equips an agent: it explains the output structure, needed post-processing (alignment), defaults, and the existence of a single-period alternative. No gaps remain despite missing output schema.

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?

Adds significant value beyond the schema: documents defaults (dimensions=['query'], row_limit=100), conveys conventions (period 1=baseline), and provides usage examples (e.g., 'use ['page'] for URL-level changes'). Schema coverage is 100% but description enriches each parameter's context.

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?

Clearly states it queries Search Console analytics twice and returns periods side-by-side. Explicitly distinguishes from sibling tool search_console_analytics_query by noting the single-period alternative.

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

Usage Guidelines5/5

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

Provides explicit guidance on when to use (two-period comparison) and when not (single period, use sibling). Also warns that the tool does not diff or merge, requiring agent to align by first key. Gives defaults and usage hints like 'period 1 is older baseline'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/logly/mureo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server