Skip to main content
Glama
modelbrain-search-console

modelbrain-search-console

Official

Compare two periods

compare_periods
Read-onlyIdempotent

Compare two date ranges side by side to see total clicks plus the queries or pages that gained and lost the most. Defaults to the last 28 days against the prior 28.

Instructions

Totals for two date ranges side by side, plus the queries or pages that gained and lost the most clicks. Defaults to the last 28 days of final data against the 28 days before.

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>"
    },
    "name": "compare_periods"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRisers and fallers to show. Default: 10
site_urlYesThe Search Console property, for example sc-domain:example.com or https://example.com/. A plain domain or page URL also works: it is matched to the right property.
dimensionNoWhat to rank risers and fallers by. Default: query
current_endNoLast day of the current period. Default: 3 days ago.
search_typeNoDefault: web
previous_endNoLast day of the earlier period. Default: the day before current_start.
current_startNoFirst day of the current period. Default: 28 days before current_end.
previous_startNoFirst day of the earlier period. Default: same length, just before the current period.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorld, so the safety profile is covered. The description adds the useful context that the comparison is based on 'final data' with a default 3-day lag, but says nothing about result size, ordering, or what happens when a dimension value disappears entirely between periods.

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?

Two sentences, front-loaded with what is returned and followed by the default window. Nothing is redundant with the title, and no sentence is filler.

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 an eight-parameter tool with no output schema, the description does the important extra work of summarizing the return shape (period totals plus top gainers and losers). It is nearly complete, with only the absence of explicit sibling routing keeping it from 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 every parameter including the four date bounds, dimension, search_type, and limit is already documented with defaults and formats. The description only echoes the date defaults and hints that dimension drives whether queries or pages are ranked; it adds no syntax or edge-case meaning beyond the schema.

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?

The description uses a specific verb-and-resource framing: it returns totals for two date ranges side by side, plus the queries or pages that gained and lost the most clicks. That clearly separates it from a single-period performance query such as search_performance, though it never names that sibling explicitly.

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?

Usage is implied by the default behavior (last 28 days of final data vs. the preceding 28 days), which tells the agent this is the go-to tool for period-over-period change analysis. There is no explicit statement of when to prefer this over search_performance, nor any exclusion or prerequisite guidance.

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