Skip to main content
Glama
Suganthan-Mohanadasan

Google Search Console MCP Server

by Suganthan-Mohanadasan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

advanced_search_analytics

Run custom Google Search Console analytics queries with flexible dimensions, filters, and search types to extract specific data cuts for in-depth performance analysis.

Instructions

Run a custom search analytics query with flexible dimensions and filters. Supports country, device, query, and page filtering, plus search type (web/image/video/news/discover/googleNews). For power users who need specific data cuts. IMPORTANT: Base your analysis ONLY on the data returned. Report exact numbers from the results. Do not speculate about causes (e.g. algorithm updates, competitor actions) unless the data explicitly supports it. If the data does not contain enough information to answer a question, say so clearly rather than guessing. PRESENTATION: Always present these results as a rich, interactive visualization using artifacts. Use summary cards for key metrics, colour-coded indicators for severity or change direction (green for positive, red for negative), bar charts or sparklines for comparisons, and tabbed sections to organise different categories of results. Make the output visually scannable and dashboard-like rather than plain text or raw tables. POSITION: position is an impression-weighted average over real impressions, blended across queries, devices and countries. It is not a rank-tracker rank. Deep positions are only recorded when a user actually reaches that part of the results, so values beyond page one rest on sparse data. Treat absolute positions as directional and prefer position deltas between periods when judging change.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoNumber of days to analyse
filtersNoDimension filters to apply
order_byNoSort by: clicks, impressions, ctr, positionclicks
site_urlNoOverride the default site URL
row_limitNoMaximum rows to return (max 500)
dimensionsNoDimensions to group by: query, page, country, device, date
search_typeNoFilter by GSC search surface. Defaults to web. Use 'image' to query Google Images data.
order_directionNoSort direction: ascending, descendingdescending

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.4.0
    • addedInput schema / properties / search_type
      Added value: +{
+  "description": "Filter by GSC search surface. Defaults to web. Use 'image' to query Google Images data.",
+  "enum": [
+    "web",
+    "image",
+    "video",
+    "news",
+    "discover",
+    "googleNews"
+  ],
+  "type": "string"
+}
  2. First observedv2.2.2

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It goes well beyond the basics by warning analysis must rely only on returned data, prohibiting speculation, requiring honest admission of insufficient data, and explaining that position is an impression-weighted average, not a rank-tracker rank, with sparse-data caveats beyond page one.

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 longer than average but structured into distinct, purposeful blocks: core functionality, analysis integrity rules, presentation expectations, and position semantics. Each section earns its place, though the presentation instructions are somewhat tangential to tool invocation and could be slightly tightened.

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?

Given no annotations and no output schema, the description covers the most important non-obvious behaviors: how to interpret position, how to present results, and how to handle uncertainty in analysis. It does not describe the exact output row structure or pagination, but the schema and order_by options already imply the returned metrics.

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?

The input schema already documents all parameters with 100% coverage, so the baseline applies. The description adds some useful context by naming the filtering dimensions and search types, and clarifies position semantics, but it does not add significant syntax-level detail beyond what the schema provides.

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 opens with a specific verb and resource: 'Run a custom search analytics query with flexible dimensions and filters.' It lists concrete filterable dimensions and search types, and says it is for power users needing specific data cuts, which distinguishes it from prepackaged sibling analytics tools.

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 clearly signals when to use this tool: for custom, flexible data cuts beyond standard reports—'For power users who need specific data cuts.' It does not explicitly name alternatives or state when not to use it, but the context among many specialized siblings makes the intended use reasonably clear.

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