Skip to main content
Glama

SEO GSC Wizard MCP

Detect traffic change points

detect_change_points
Read-only

Finds the dates where a property's clicks or impressions shifted to a new sustained level (step changes / level shifts), reporting the before vs after average and the % change at each break. Unlike anomaly detection (one-off spikes), this locates durable regime changes: a migration, an algorithm update, a redesign. Each date is the day the shift is strongest (the first day of the new level). Days without rows count as zero, so a drop to zero (deindexing) is a change point; coverage reports how an empty tail at the end of the window was treated. Reads the ClickHouse warehouse when available, else the live Search Console API. When a shift starts from a zero baseline (beforeMean 0) it has no percentage: changePercent is 0 by convention, which does not mean no change; describe it as new traffic from zero using afterMean.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoTrailing days of daily data to analyze (min 14, default 180).
metricNoWhich metric to segment.clicks
siteUrlYes
sensitivityNoMean-shift threshold in std-devs: lower = more sensitive (more change points). Default 2.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNo
countNo
rangeNo
metricNo
siteUrlNo
coverageNo
dataSourceNo
sensitivityNo
changePointsNo
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"
      +        },
      +        "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