Skip to main content
Glama

Search Console summary

search_console_summary
Read-only

Retrieve site-wide Google Search clicks, impressions, CTR, and average position for a selected period, compared with the prior equivalent period to show changes.

Instructions

A website's total organic Google Search clicks, impressions, CTR and average position over a window, next to the same number of days before it, with the change. Site-wide totals, more complete than adding up per-query rows. 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_summary"
  }
}

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
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

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?

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral context beyond that: it discloses the comparison against the previous same-length period, notes that site-wide totals are more complete than per-query rows, and reinforces that nothing is changed. It does not cover rate limits or authorization, but with annotations present this is acceptable.

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 description is a single tight sentence with the core metrics and comparison front-loaded. Every phrase contributes useful information, and the closing 'Changes nothing' is a compact safety reinforcement.

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 a read-only summary tool with rich schema descriptions and clear annotations, the description is nearly complete. It explains the returned metrics, the comparative period, the site-wide scope, and the non-mutating nature; the main omission is explicit routing to the closest sibling performance tool.

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 the parameters days, fresh, start_date, and end_date are already documented in the schema. The description references the window and the comparison period, but adds no new meaning about parameter interactions or formats beyond what the schema provides.

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 states clearly that the tool returns site-wide organic Google Search totals for clicks, impressions, CTR, and average position over a window, compared to the prior equivalent window. It distinguishes itself from per-query aggregation but does not explicitly name the closest sibling, search_console_performance, so sibling differentiation is only partial.

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?

It implies when to use the tool by saying site-wide totals are more complete than adding up per-query rows. However, it does not name an alternative tool or state explicit when-not conditions, leaving the agent to infer the distinction from the brief scope note.

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