Google Search Console MCP

Identify SEO Quick Wins

insights.quick_wins

Read-only

Identify search queries ranking in striking-distance positions (8-20) with sufficient impressions to prioritize SEO quick wins. Returns engagement metrics to guide optimization.

Instructions

Find search queries with at least the requested impressions that rank in a configurable striking-distance position range (8-20 by default). Returns clicks, impressions, CTR, and average position; CTR is context, not an eligibility filter. Pagination metadata flags when the local 100,000-row safety ceiling stopped fetching; a false flag does not guarantee Search Console returned every underlying row.

Input Schema

TableJSON Schema

Name	Required	Description
`end_date`	Yes	End date (inclusive) in YYYY-MM-DD format. Note the 2-3 day GSC data lag.
`site_url`	Yes	The Search Console property identifier, exactly as returned by sites.list. Two formats exist: domain properties use 'sc-domain:example.com'; URL-prefix properties use the full URL including protocol and trailing slash, e.g. 'https://www.example.com/'. Passing the wrong format returns a permission error even when the user owns the site — call sites.list first if unsure.
`start_date`	Yes	Start date (inclusive) in YYYY-MM-DD format.
`max_position`	No	Maximum average position to target (inclusive). Must be greater than 0. Default is 20.
`min_position`	No	Minimum average position to target (inclusive). Must be greater than 0. Default is 8.
`min_impressions`	No	Minimum impressions required to consider a query. Must be at least 0. Default is 100.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`pagination`	Yes
`quick_wins`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 29, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description adds valuable behavior beyond the readOnlyHint and openWorldHint annotations: it clarifies that CTR is reporting context, not a filter, and discloses the 100,000-row safety ceiling with pagination metadata. The caveat that a false flag does not guarantee full Search Console data is especially transparent and prevents over-trust in the result set.

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, each earning its place: the first defines the core query filter, the second lists return metrics and clarifies CTR's role, the third discloses pagination limitations. It is front-loaded and free of filler.

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

Completeness5/5

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

Given the output schema, annotations, and 100% parameter coverage, the description is complete for safe invocation. It covers defaults, return columns, the non-filter semantics of CTR, and the pagination ceiling. No critical operational detail is missing.

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 each parameter already carries meaning. The description adds some framing around the defaults (8-20 striking-distance range) and confirms min_impressions is an eligibility threshold, but it does not need to compensate for missing parameter documentation.

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?

The description names a specific resource ('search queries') and a precise eligibility shape: impressions threshold plus a striking-distance position range. It clearly differentiates this from sibling tools like insights.cannibalization or insights.content_decay by framing the output as quick wins based on position and impressions.

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

Usage Guidelines4/5

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

The description gives a clear usage context: call this when the agent needs to surface queries just outside the top results that are worth optimizing. It does not explicitly name alternative tools or when-not-to-use conditions, but the eligibility criteria are specific enough to steer selection.

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

Deploy Server