Skip to main content
Glama

Search Console trend

search_console_trend
Read-only

Compare Search Console performance across two equal periods to reveal rising, falling, new, and lost queries and pages, plus position changes, without altering data.

Instructions

Compares a window with the same number of days right before it, query by query and page by page: rising, falling, new and lost queries, rising searches the site is losing position on, and rising and falling pages. Totals are the site's true totals. Changes nothing.

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": "search_console_trend"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days, ending 3 days ago (yesterday with fresh)
freshNoInclude the last 2-3 days, which Google is still filling in (they read low). Use to check something from the last few days
limitNoMost rows in each list
end_dateNoExact last day, YYYY-MM-DD
site_urlYesSearch Console property exactly as search_console_sites lists it, e.g. sc-domain:example.com or https://www.example.com/
start_dateNoExact first day, YYYY-MM-DD
min_impressionsNoSkip queries and pages under this many impressions in both windows
exclude_query_regexNoLeave out queries matching this RE2 regex, typically the brand name, e.g. (?i)acme|ac me

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.46.0
    • changedInput schema / properties / start_date / description
      Previous value: -"Exact first day, YYYY-MM-DD. Pass with end_date to use exact dates instead of days"New value: +"Exact first day, YYYY-MM-DD"
  2. First observedv0.11.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint=false, so "Changes nothing" is largely reinforcing, but the description adds a genuinely non-obvious behavioral fact: "Totals are the site's true totals," warning that the per-list rows are truncated samples that do not sum to the totals. That is exactly the kind of caveat an agent needs before reporting numbers. It does not restate the 3-day data lag or the per-list row cap, which live in the schema, so it falls short of a 5.

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?

Three sentences, front-loaded with the comparison definition followed by the output buckets, and zero redundant filler. The dense clause list of result categories is efficient rather than bloated, and the closing safety note is short.

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?

With 8 parameters, no output schema, and rich annotations, the description covers the essential shape of the result (which lists come back) and the totals-vs-rows caveat. It does not mention pagination/limits behavior or that results are confined to the top rows by default, but the schema's limit description covers that. Complete enough for an agent to call it correctly.

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 (days, fresh, limit, dates, min_impressions, exclude_query_regex, site_url) is already documented in detail, including the 3-day lag and the brand-regex tip. The description adds no parameter-level meaning beyond the schema, which is the correct baseline of 3 when the schema does the heavy lifting.

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 precise verb ("compares") and defines the resource: a look-back window versus the immediately preceding equal-length window, split query-by-query and page-by-page. It enumerates the distinct output buckets (rising, falling, new, lost queries, position-losing rising searches, rising/falling pages), which makes the tool clearly distinguishable from a plain performance report. It stops short of naming which sibling to use instead (e.g. search_console_performance), so a 4 rather than a 5.

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 only implied through the description of what the comparison returns; there is no explicit "use this when you want to see what changed over time versus search_console_performance." No prerequisites or exclusions are stated, although the phrase "rising searches the site is losing position on" hints at the diagnosis use case. Adequate but leaves the agent to infer when to pick this over search_console_opportunities or search_console_performance.

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