Google Search Console by Get MCP Ads

Overview Schema Source Related Servers Discussions Admin

gsc get data freshness

gsc_get_data_freshness

Read-onlyIdempotent

Determine the data cutoff date for Search Console Search Analytics by scanning recent daily rows, helping you confirm freshness for a property or search type.

Instructions

Detect the most recent date with Search Analytics data by querying recent daily rows.

Input Schema

Name	Required	Description	Default
`siteUrl`	No	Search Console property URL, e.g. https://example.com/ or sc-domain:example.com. Uses GSC_SITE_URL when omitted.
`searchType`	No	Search surface to report, such as web, image, video, news or Discover. Availability depends on the property.	web
`lookbackDays`	No	Recent days to scan for daily data. Max 30.

Output Schema

Name	Required	Description	Default
`result`	Yes	Original tool result: parsed JSON when the text is JSON, otherwise the text or multiple MCP content blocks. Provider fields depend on the selected query.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.1.1Oct 30, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / properties / result / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  },
-  {
-    "items": {},
-    "type": "array"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  {
+    "items": {},
+    "type": "array"
+  },
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

First observedv2.0.1Sep 23, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds a small amount of behavioral context — that the detection works by scanning recent daily rows — but says nothing about cost, API call volume, rate limits, or what happens when no data is found within the lookback window.

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?

A single front-loaded sentence that leads with the outcome and ends with the mechanism; there is no filler and nothing is buried.

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

Completeness3/5

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

An output schema exists, so return values needn't be explained, and read-only/idempotent behavior is covered by annotations. What's missing is the operational context an agent still needs: which counts as valid output when no data is found, and how this differs from the other freshness-flavored sibling.

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 siteUrl, searchType and lookbackDays (including the 3–30 bound) are fully documented in the schema. The description's reference to "recent daily rows" loosely gestures at lookbackDays but adds no format or defaulting behavior, so the baseline 3 applies.

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?

States a specific verb ("detect") and a precise resource/outcome ("the most recent date with Search Analytics data"), plus the mechanism ("querying recent daily rows"). That is enough to distinguish it from analytics-query siblings, though it never names the similarly-titled gsc_monitor_indexation_freshness, which an agent could easily confuse it with.

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 when-to-use guidance at all: it doesn't say to call this before gsc_query_search_analytics to avoid querying stale dates, nor when to prefer gsc_monitor_indexation_freshness instead. The only usage context is implicitly inferred from the word "detect".

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