Google Search Console Audit MCP

Overview Schema Source Related Servers Discussions Admin

gsc_performance_overview

Read-onlyIdempotent

Compare site-wide search performance totals against the prior period, showing percentage changes on all metrics to quickly determine if your site is trending up or down.

Instructions

Site totals for a period, compared with the preceding one by default.

Start here: it answers "is the site up or down" in one call, with the percentage change on every metric. position_delta is negative when the average position improves.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`days`	No	Rolling window length ending today.
`type`	No	web, image, video, news, discover or googleNews.	web
`period`	No	Named range: last_7_days, last_28_days, last_3_months, last_month, this_month, last_16_months.
`date_to`	No	End date YYYY-MM-DD. Defaults to today.
`no_cache`	No	Bypass the response cache for this call.
`site_url`	Yes	`sc-domain:example.com` for a domain property, or `https://example.com/` with the trailing slash for a URL-prefix property. Call gsc_sites if unsure.
`date_from`	No	Start date YYYY-MM-DD. Overrides period and days.
`data_state`	No	`all` (default, includes today's partial data) or `final`.
`compare_previous`	No	Also fetch the equally long preceding period.

Output Schema

TableJSON Schema

Name	Required	Default
`delta`	No
`current`	Yes
`date_to`	Yes
`previous`	No
`site_url`	Yes
`date_from`	Yes
`data_state`	No	all
`previous_range`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed25 schema fields changedv3.0.1Aug 28, 2026

addedInput schema / properties / compare_previous

Added value: +{
+  "default": true,
+  "description": "Also fetch the equally long preceding period.",
+  "title": "Compare Previous",
+  "type": "boolean"
+}

addedInput schema / properties / data_state

Added value: +{
+  "default": "",
+  "description": "`all` (default, includes today's partial data) or `final`.",
+  "title": "Data State",
+  "type": "string"
+}

addedInput schema / properties / date_from / default
```
Added value: +""
```

addedInput schema / properties / date_from / description

Added value: +"Start date YYYY-MM-DD. Overrides period and days."

addedInput schema / properties / date_to / default
```
Added value: +""
```

addedInput schema / properties / date_to / description

Added value: +"End date YYYY-MM-DD. Defaults to today."

addedInput schema / properties / days

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Rolling window length ending today.",
+  "title": "Days"
+}

addedInput schema / properties / no_cache

Added value: +{
+  "default": false,
+  "description": "Bypass the response cache for this call.",
+  "title": "No Cache",
+  "type": "boolean"
+}

addedInput schema / properties / period

Added value: +{
+  "default": "",
+  "description": "Named range: last_7_days, last_28_days, last_3_months, last_month, this_month, last_16_months.",
+  "title": "Period",
+  "type": "string"
+}

addedInput schema / properties / site_url / description

Added value: +"`sc-domain:example.com` for a domain property, or `https://example.com/` with the trailing slash for a URL-prefix property. Call gsc_sites if unsure."

addedInput schema / properties / type

Added value: +{
+  "default": "web",
+  "description": "web, image, video, news, discover or googleNews.",
+  "title": "Type",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "site_url",
-  "date_from",
-  "date_to"
-]New value: +[
+  "site_url"
+]

addedOutput schema / $defs

Added value: +{
+  "Delta": {
+    "description": "Percentage change between two periods. Position improves when it goes down.",
+    "properties": {
+      "clicks_pct": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Clicks Pct"
+      },
+      "ctr_pct": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Ctr Pct"
+      },
+      "impressions_pct": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Impressions Pct"
+      },
+      "position_delta": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Absolute change in average position; negative means an improvement",
+        "title": "Position Delta"
+      }
+    },
+    "title": "Delta",
+    "type": "object"
+  },
+  "Totals": {
+    "description": "Aggregate metrics for one period.",
+    "properties": {
+      "clicks": {
+        "default": 0,
+        "title": "Clicks",
+        "type": "integer"
+      },
+      "ctr": {
+        "default": 0,
+        "description": "Click-through rate as a fraction, 4 decimals",
+        "title": "Ctr",
+        "type": "number"
+      },
+      "impressions": {
+        "default": 0,
+        "title": "Impressions",
+        "type": "integer"
+      },
+      "position": {
+        "default": 0,
+        "description": "Average position, 1 decimal",
+        "title": "Position",
+        "type": "number"
+      }
+    },
+    "title": "Totals",
+    "type": "object"
+  }
+}

addedOutput schema / description

Added value: +"Site totals for a period, optionally compared with the preceding one."

addedOutput schema / properties / current

Added value: +{
+  "$ref": "#/$defs/Totals"
+}

addedOutput schema / properties / data_state

Added value: +{
+  "default": "all",
+  "title": "Data State",
+  "type": "string"
+}

addedOutput schema / properties / date_from

Added value: +{
+  "title": "Date From",
+  "type": "string"
+}

addedOutput schema / properties / date_to

Added value: +{
+  "title": "Date To",
+  "type": "string"
+}

addedOutput schema / properties / delta

Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/Delta"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedOutput schema / properties / previous

Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/Totals"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedOutput schema / properties / previous_range

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Previous Range"
+}

removedOutput schema / properties / result

Removed value: -{
-  "title": "Result",
-  "type": "string"
-}

addedOutput schema / properties / site_url

Added value: +{
+  "title": "Site Url",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "result"
-]New value: +[
+  "site_url",
+  "date_from",
+  "date_to",
+  "current"
+]

changedOutput schema / title

Previous value: -"gsc_performance_overviewOutput"New value: +"Overview"

First observedv2.0.2Apr 23, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already indicate a safe read-only operation. The description adds useful behavioral context beyond that: comparison with the previous period is the default, and position_delta semantics ('negative when the average position improves') are explained. This helps the agent interpret results correctly.

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?

Three tight sentences, each earning its place: the first states function, the second gives the primary use case, and the third clarifies an important metric interpretation. Information is front-loaded with no redundancy.

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

Completeness5/5

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

For a read-only overview tool with a full input schema and an output schema present, the description provides all the behavioral guidance an agent needs: what it returns, the default comparison behavior, and the key metric nuance. Nothing important is missing.

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?

Schema description coverage is 100%, so the parameters are already fully documented. The description adds no new parameter-level meaning; it mainly reinforces compare_previous default behavior implicitly. This is the expected baseline when the schema carries the load.

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 tool's function: 'Site totals for a period' with comparison to the preceding period and 'percentage change on every metric.' The 'Start here' framing and 'is the site up or down' metaphor make the purpose immediately understandable, though no sibling tool is explicitly named for differentiation.

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 tells the agent when to use this tool: 'Start here: it answers "is the site up or down" in one call.' This provides clear context for choosing this tool first, but it does not explicitly state when to prefer alternatives or when not to use it.

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

Deploy Server