Skip to main content
Glama

SEO GSC Wizard MCP

Detect traffic anomalies

detect_anomalies
Read-only

Flags statistically anomalous days in a property's Search Console series for a chosen metric (clicks, impressions, CTR, or position). Uses a robust Modified Z-score with median absolute deviation and day-of-week baselines (mean absolute deviation when most days are identical, as on a low-traffic property), then scores each spike/drop by severity (critical → info). Days without rows count as zero for clicks and impressions, so a drop to zero (deindexing) is flagged; the 21-day minimum is measured in calendar days from the first day with data. CTR and position use only days with impressions. coverage reports the days analysed and how an empty tail at the end of the window was treated. Good for "did something break / spike on a specific day?". Reads the ClickHouse warehouse when available, else the live Search Console API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoTrailing days of daily data to analyze (min 21, default 90).
metricNoWhich metric to scan for anomalies.clicks
siteUrlYes
sensitivityNoModified Z-score threshold: lower = more sensitive (more anomalies). Default 3.5; 3-4 is typical.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNo
rangeNo
metricNo
siteUrlNo
summaryNo
coverageNo
anomaliesNo
dataSourceNo
sensitivityNo
dataMaturityNo
settledThroughNo
warehouseLatestDateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / coverage
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": false,
      +      "properties": {
      +        "calendarDays": {
      +          "$ref": "#/properties/sensitivity"
      +        },
      +        "daysAnalyzed": {
      +          "$ref": "#/properties/sensitivity"
      +        },
      +        "daysWithData": {
      +          "$ref": "#/properties/sensitivity"
      +        },
      +        "firstDataDate": {
      +          "$ref": "#/properties/siteUrl"
      +        },
      +        "lastDataDate": {
      +          "$ref": "#/properties/siteUrl"
      +        },
      +        "trailingGap": {
      +          "anyOf": [
      +            {
      +              "additionalProperties": false,
      +              "properties": {
      +                "lastDataDate": {
      +                  "$ref": "#/properties/siteUrl"
      +                },
      +                "missingDays": {
      +                  "$ref": "#/properties/sensitivity"
      +                },
      +                "note": {
      +                  "$ref": "#/properties/siteUrl"
      +                },
      +                "status": {
      +                  "$ref": "#/properties/siteUrl"
      +                }
      +              },
      +              "type": "object"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        },
      +        "zeroFilledDays": {
      +          "$ref": "#/properties/sensitivity"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / warehouseLatestDate
      Added value: +{
      +  "$ref": "#/properties/siteUrl"
      +}
  2. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources