searchconsole-mcp

Query search analytics

gsc_search_analytics

Pull Search Console search data—clicks, impressions, CTR, and average position—grouped by query, page, country, device, or date. Set custom date ranges and filters to analyze SEO performance.

Instructions

Run a Search Console search-analytics query: clicks, impressions, CTR and average position grouped by dimensions (query, page, country, device, date). Dates default to the last 28 days.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gsc_search_analytics"
  }
}

Input Schema

Name	Required	Description	Default
`endDate`	No	End date YYYY-MM-DD (inclusive), defaults to today
`siteUrl`	No	Property, e.g. "sc-domain:example.com". Falls back to GSC_DEFAULT_SITE.
`rowLimit`	No
`startRow`	No
`dataState`	No	"all" includes fresh (partial) data	final
`startDate`	No	Start date YYYY-MM-DD (inclusive), defaults to today minus 28 days
`dimensions`	No	Dimensions to group by; up to 3 per API limit when combining
`searchType`	No		web
`aggregationType`	No		auto
`dimensionFilterGroups`	No	Optional filter groups, e.g. filter queries containing 'blog'

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 23, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden; it does not mention side effects, permissions, rate limits, or the structure of the response, leaving behavioral aspects undisclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence but packs essential information about the operation, metrics, and defaults without unnecessary verbosity.

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

Completeness2/5

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

Given the tool's complexity with 10 parameters and nested filter groups, the description is too brief; it omits explanations of output format, available search types, aggregation options, and filter semantics, making it insufficient for full understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds minimal insight beyond the schema; it notes the default date range and valid dimensions, but many parameters like searchType, aggregationType, and filters are not explained in the description, and the schema already covers most descriptions.

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 clearly states the action (run a query) and the resource (Search Console search-analytics), and lists the returned metrics and grouping dimensions, making it distinct from sibling tools about sites and sitemaps.

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 does not provide any guidance on when to use this tool versus other tools, or any conditions that would trigger its use; it only states what it does.

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

Deploy Server