Google Search Console MCP

Top pages by clicks

top_pages

Read-onlyIdempotent

Rank pages on a Search Console property by Google Search clicks, with impressions, CTR, and average position.

Instructions

The pages on a property earning the most clicks from Google Search, with impressions, CTR and average position. Defaults to the last 28 days ending three days ago.

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

Input Schema

Name	Required	Description
`days`	No
`site`	Yes	The Search Console property. Either a URL-prefix property ("https://navid.me/", trailing slash included) or a domain property ("sc-domain:navid.me"). A bare hostname is read as a domain property. Call list_sites for the exact strings this account owns, because the two shapes are different properties and mixing them up returns a 403.
`type`	No	Which surface to report on. Defaults to web. "discover" and "googleNews" carry no query or device dimension at all, so asking for one returns an error rather than empty rows.
`limit`	No
`account`	No	Which signed-in Google account to act as, by email. Omit to use the default. Call list_accounts to see what is signed in.
`country`	No	Three-letter country code, e.g. "usa".
`query_filter`	No	Only clicks that came from queries containing this.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.3.0Oct 5, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
First observedv0.1.0Sep 2, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the bar is lower. The description still contributes a non-obvious behavioral fact — the data lag ('ending three days ago') — which the agent needs to interpret freshness correctly, though it says nothing about pagination, rate limits, or how limit interacts with large result sets.

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 with no filler: the first front-loads what is returned, the second front-loads the default time window. Nothing is repeated from the title or annotations.

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

Completeness3/5

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

For a 7-parameter analytics tool with no output schema, the description does list the returned measures, which partially substitutes for a return schema. However, it omits how limit/pagination behaves, how this differs from query_search_analytics or top_queries, and any prerequisite such as needing a verified property, leaving meaningful gaps.

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 coverage is 71%, so the schema already documents site, type, account, country, and query_filter, including the 403 warning for mismatched property shapes and the error behavior for discover/googleNews. The description only adds semantics for the date window (days default 28, ending three days ago) and leaves limit entirely undocumented in both places, so it compensates only partially.

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?

Names a specific resource (pages on a property) and the ranking metric (most clicks from Google Search), plus the returned measures (impressions, CTR, average position). An agent can distinguish this from the sibling top_queries without opening either schema, since one ranks pages and the other ranks queries.

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?

The description states the default reporting window ('last 28 days ending three days ago'), which is useful context, but gives no explicit when-to-use or when-not-to-use guidance against alternatives such as top_queries, compare_periods, or query_search_analytics. Usage is implied by the resource name rather than stated.

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