Skip to main content
Glama
thenavidm

Google Search Console MCP

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Top search queries by clicks

top_queries
Read-onlyIdempotent

Fetches search queries ranked by clicks for a Search Console property, with impressions, CTR, and average position. Defaults to the last 28 days to avoid empty results from lag.

Instructions

The search queries bringing the most clicks to a property, with impressions, CTR and average position. Defaults to the last 28 days ending three days ago, because Search Console lags and a window ending today reads as empty.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoWindow length.
siteYesThe 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.
typeNoWhich 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.
limitNo
accountNoWhich signed-in Google account to act as, by email. Omit to use the default. Call list_accounts to see what is signed in.
countryNoThree-letter country code, e.g. "usa", "gbr", "swe".
page_filterNoOnly queries that landed on pages whose URL contains this, e.g. "/blog/".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare the safe read-only/idempotent profile, and the description adds genuinely useful behavioral context beyond them: the default window ends three days ago because Search Console lags and a window ending today reads as empty. It stops short of covering pagination or rate-limit behavior.

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, zero filler, with the metric list front-loaded and the default-window caveat immediately following. Every clause carries information.

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 7-parameter read tool with no output schema, the description usefully enumerates returned metrics (impressions, CTR, average position) and explains the default window. The main gap is the absence of routing guidance versus overlapping siblings, but the parameter and return picture is otherwise complete.

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 86%, so the schema already documents parameters richly (site, type, account, page_filter, country all have detailed descriptions). The description only adds the default-window rationale for 'days', which is marginal over what the schema provides. Baseline 3 is appropriate.

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?

States a specific verb and resource ('search queries bringing the most clicks to a property') and enumerates the returned metrics. It implicitly distinguishes itself from the sibling top_pages by operating on queries rather than pages, but it never explicitly names or contrasts with alternatives like top_pages or query_search_analytics.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the default window rationale but gives no guidance on when to choose this tool over siblings such as top_pages or query_search_analytics, nor any exclusions or prerequisites. The agent must infer usage purely from the resource name.

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

Deploy Server

Other Tools