Skip to main content
Glama
Akxan

google-seo-mcp

by Akxan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Site snapshot (one-call overview)

gsc_site_snapshot
Read-onlyIdempotent

Get a site performance snapshot with period-over-period totals, top queries and pages, device/country splits, and page winners/losers to answer 'how is the site doing' in one call.

Instructions

One call that answers 'how is the site doing': totals for the period and the previous period of equal length (clicks, impressions, CTR, position with deltas), top queries, top pages, device and country split, and the biggest winners/losers by page. Use this first when asked for an overview or a report.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topNo
daysNo
filtersNoScope the analysis, e.g. page contains '/es/' for one language folder. Defaults to the whole property.
siteUrlYesSearch Console property, e.g. 'sc-domain:example.com' (see gsc_list_sites).
dataStateNo'all' includes fresh, not yet final data and ends the window yesterday instead of 3 days ago.final
searchTypeNoweb
aggregationTypeNobyPage vs byProperty changes the reported average position.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.10.0
    • addedInput schema / properties / aggregationType
      Added value: +{
+  "description": "byPage vs byProperty changes the reported average position.",
+  "enum": [
+    "auto",
+    "byPage",
+    "byProperty"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / dataState
      Added value: +{
+  "default": "final",
+  "description": "'all' includes fresh, not yet final data and ends the window yesterday instead of 3 days ago.",
+  "enum": [
+    "final",
+    "all"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / filters
      Added value: +{
+  "description": "Scope the analysis, e.g. page contains '/es/' for one language folder. Defaults to the whole property.",
+  "items": {
+    "properties": {
+      "dimension": {
+        "enum": [
+          "query",
+          "page",
+          "country",
+          "device",
+          "searchAppearance"
+        ],
+        "type": "string"
+      },
+      "expression": {
+        "description": "Value; device: DESKTOP/MOBILE/TABLET, country: 3-letter code like 'usa'.",
+        "type": "string"
+      },
+      "operator": {
+        "default": "equals",
+        "enum": [
+          "equals",
+          "notEquals",
+          "contains",
+          "notContains",
+          "includingRegex",
+          "excludingRegex"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "dimension",
+      "expression"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • changedInput schema / properties / siteUrl / description
      Previous value: -"Search Console property, e.g. 'sc-domain:example.com' or 'https://example.com/' (see gsc_list_sites)."New value: +"Search Console property, e.g. 'sc-domain:example.com' (see gsc_list_sites)."
  2. Changed2 schema fields changedv0.5.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / siteUrl / description
      Previous value: -"Property URL exactly as shown in Search Console, e.g. 'https://example.com/' or 'sc-domain:example.com'. Use gsc_list_sites to discover it."New value: +"Search Console property, e.g. 'sc-domain:example.com' or 'https://example.com/' (see gsc_list_sites)."
  3. First observedv0.3.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already establish that this is read-only, idempotent, and non-destructive. The description adds the fact that it is a single call and that it computes a previous-period comparison, but it does not disclose behavioral traits like data freshness, rate limits, or how winners/losers are determined. It does not contradict the 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?

Two sentences with no filler: the first front-loads the core promise and content, the second gives a direct usage directive. Every clause contributes value.

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?

For an overview tool, the description conveys the main return categories and the recommended first-use context. With no output schema, it could say more about ordering/limits or how deltas are computed, but the listed components give a solid mental model. Schema covers parameter defaults and filtering reasonably well.

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 does not explain any parameters, even though 7 parameters exist and schema description coverage is only 57%. Parameters like 'top', 'days', and 'searchType' lack meaningful schema descriptions, and the description provides no compensating detail. The description focuses entirely on output, adding nothing beyond the input schema.

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 purpose: a one-call overview of site performance, and enumerates concrete output components (totals with deltas, top queries/pages, device/country split, winners/losers). It distinguishes itself from more granular siblings by being the 'one-call overview' tool.

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 explicitly says to use this tool first when an overview or report is requested, which gives clear usage context. It does not name alternative tools or state exclusions, so it falls short of the fullest 5-level guidance.

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