Skip to main content
Glama

search_console_analytics_compare_periods

Compare Search Console analytics across two date ranges, returning both periods' data side-by-side for direct analysis of changes in queries, clicks, impressions, CTR, and position.

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?

With no annotations provided, the description fully covers behavioral traits: read-only, two REST calls per invocation, defaults, output structure, and raw data alignment requirements. No contradictions.

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?

Description is concise (5 sentences), front-loaded with the primary action, and every sentence adds value without redundancy.

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?

Given no output schema, the description clearly explains the return format. It covers defaults, constraints, and references the sibling tool for single-period queries. Complete for a comparison tool.

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

Parameters4/5

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

Schema coverage is 100% with descriptions, but the tool description adds valuable context: period 1 is older/baseline, period 2 newer/comparison, and explains the purpose of dimensions and row_limit. Adds meaning beyond schema.

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?

Description clearly states the tool queries Search Console analytics for two periods and returns them side-by-side. It specifies the verb (query), resource (Search Console analytics), and distinguishes from the single-period sibling tool search_console_analytics_query.

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?

Explicitly states when to use (comparing two periods) and when not (use single-period tool for a single query). Also explains that the tool does not diff or merge, so the agent must align rows.

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