Google Search Console MCP Intel Engine

Overview Schema Source Related Servers Score Discussions Admin

get_search_analytics

Read-onlyIdempotent

Retrieve Google Search Console search analytics metrics (clicks, impressions, CTR, position) by specifying dimensions, filters, and date ranges to analyze performance for queries, pages, devices, or countries.

Instructions

Retrieve Google Search Console search analytics data.

Args: dimensions: List of dimensions from: country, device, page, query, searchAppearance, date start_date: Start date in YYYY-MM-DD format (defaults to 30 days ago) end_date: End date in YYYY-MM-DD format (defaults to 3 days ago) filters: List of filter objects (e.g., [{"dimension": "country", "operator": "equals", "expression": "usa"}]) search_type: Type of search ('web', 'image', 'video', 'news', 'discover', 'googleNews') row_limit: Maximum number of rows to return (max 25000) start_row: Starting row for pagination (0-based) summary_only: If True, returns only aggregated totals (Token Efficient) intent: Short plain-English description of what the user is trying to learn/accomplish. E.g. "which queries drive clicks to the pricing page", "mobile vs desktop performance last month".

Returns: Dictionary containing search analytics data with clicks, impressions, ctr, and position metrics.

Input Schema

TableJSON Schema

Name	Required	Default
`intent`	No
`filters`	No
`end_date`	No
`row_limit`	No
`start_row`	No
`dimensions`	No
`start_date`	No
`search_type`	No	web
`summary_only`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed21 schema fields changedv0.10.1Aug 11, 2026

addedInput schema / properties / dimensions / items
```
Added value: +{
+  "type": "string"
+}
```

changedInput schema / properties / dimensions / title

Previous value: -"dimensions"New value: +"Dimensions"

changedInput schema / properties / dimensions / type
```
Previous value: -"string"New value: +"array"
```

addedInput schema / properties / end_date / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / end_date / title

Previous value: -"end_date"New value: +"End Date"

removedInput schema / properties / end_date / type
```
Removed value: -"string"
```

addedInput schema / properties / filters / anyOf

Added value: +[
+  {
+    "items": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / filters / title

Previous value: -"filters"New value: +"Filters"

removedInput schema / properties / filters / type
```
Removed value: -"string"
```

addedInput schema / properties / intent

Added value: +{
+  "default": null,
+  "title": "Intent",
+  "type": "string"
+}

changedInput schema / properties / row_limit / title

Previous value: -"row_limit"New value: +"Row Limit"

changedInput schema / properties / row_limit / type
```
Previous value: -"string"New value: +"integer"
```

changedInput schema / properties / search_type / title

Previous value: -"search_type"New value: +"Search Type"

addedInput schema / properties / start_date / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / start_date / title

Previous value: -"start_date"New value: +"Start Date"

removedInput schema / properties / start_date / type
```
Removed value: -"string"
```

changedInput schema / properties / start_row / title

Previous value: -"start_row"New value: +"Start Row"

changedInput schema / properties / start_row / type
```
Previous value: -"string"New value: +"integer"
```

changedInput schema / properties / summary_only / title

Previous value: -"summary_only"New value: +"Summary Only"

changedInput schema / properties / summary_only / type
```
Previous value: -"string"New value: +"boolean"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "SearchAnalyticsResult": {
+      "properties": {
+        "data": {
+          "items": {
+            "additionalProperties": true,
+            "type": "object"
+          },
+          "title": "Data",
+          "type": "array"
+        },
+        "error": {
+          "title": "Error",
+          "type": "string"
+        },
+        "metadata": {
+          "additionalProperties": true,
+          "title": "Metadata",
+          "type": "object"
+        },
+        "summary": {
+          "additionalProperties": true,
+          "title": "Summary",
+          "type": "object"
+        }
+      },
+      "title": "SearchAnalyticsResult",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "result": {
+      "anyOf": [
+        {
+          "$ref": "#/$defs/SearchAnalyticsResult"
+        },
+        {
+          "type": "string"
+        }
+      ],
+      "title": "Result"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "get_search_analyticsOutput",
+  "type": "object"
+}

First observedv0.6.0Aug 3, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare read-only, open-world, and idempotent hints. The description adds useful context: summary_only token efficiency, start_row pagination, and return metric names. No contradictions with annotations.

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?

Description is well-organized with a one-sentence purpose, an Args list, and a Returns line. All sentences provide unique value; no redundancy.

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?

Despite 9 optional parameters, the description covers all key behaviors: pagination, token-efficient summary, date formats, and return metrics. With an output schema present, return details need not be exhaustive. Could mention filter operators or dimension combinations, but not critical.

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

Parameters5/5

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

Schema coverage is 0%, so description carries full burden. It thoroughly explains all 9 parameters with types, examples, defaults, and max rows, going beyond the schema. The intent parameter is clarified with a plain-English example.

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 states a specific verb ('Retrieve') and resource ('Google Search Console search analytics data'), clearly differentiating from siblings like list_gsc_sites and list_available_dimensions.

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?

No explicit guidance on when to use this tool vs alternatives like list_gsc_sites or list_available_dimensions. It implies analytics retrieval but doesn't state exclusions or prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/surendranb/google-search-console-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server