Google Search Console MCP

Overview Schema Source Related Servers Discussions Admin

Query Search Analytics

gsc_search_analytics

Query Search Console data for clicks, impressions, CTR, and position across single, selected, or all properties. Apply filters and dimensions to uncover search performance insights.

Instructions

Run a Search Analytics query for one property, selected properties, or all properties. Returns clicks, impressions, CTR, and average position.

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": {
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "gsc_search_analytics"
  }
}

Input Schema

Name	Required	Default
`type`	No	web
`endDate`	Yes
`filters`	No
`siteUrl`	No
`allSites`	No
`rowLimit`	No
`siteUrls`	No
`startRow`	No
`dataState`	No	final
`startDate`	Yes
`dimensions`	No
`aggregationType`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

C2.7/5.0

Behavior3/5

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

Annotations are absent, so the description carries the full burden of behavioral disclosure. It conveys a read-only query behavior and enumerates returned metrics, which is useful. But it omits pagination behavior, row limits, aggregation semantics, or any mention that results may be filtered or grouped by dimensions, which are significant query behaviors.

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

Conciseness3/5

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

The two sentences are clear and free of filler, front-loading the action and scope. However, for a 12-parameter tool, this brevity leaves out critical guidance; it is efficient but not appropriately sized.

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?

With no output schema and low schema coverage, the description should compensate by explaining the query flow, required date parameters, output shape, and constraints. It only states scope and metrics, leaving most parameter semantics and behavioral context undefined, which is inadequate for correct invocation.

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

Parameters1/5

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

Schema description coverage is 0% and the description does not mention any parameters. Key inputs like startDate, endDate, dimensions, filters, siteUrl/allSites, rowLimit, and aggregationType are left undocumented, so the description adds no semantic value beyond the bare schema.

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 uses a specific verb ('Run') and resource ('Search Analytics query'), and explicitly names the scope (one, selected, or all properties) and output metrics (clicks, impressions, CTR, average position). However, it does not differentiate from gsc_top_queries or gsc_keyword_opportunities, which likely overlap in search analytics data, so it lacks explicit sibling distinction.

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 provides no guidance on when to use this tool versus alternatives like gsc_top_queries. There are no exclusions, prerequisites, or context about which workload it fits. An agent must infer usage solely from the tool name.

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

Deploy Server