Website Auditor MCP

Monitoring status summary

get_monitoring_status

Read-only

Check monitoring status across all tracked websites. Get AI-visibility scores, last and next scheduled runs, and recent changes per domain in one summary.

Instructions

Get a glanceable summary of monitoring status across all tracked websites. Use this when someone asks "how are my tracked sites doing," "what's my current AI visibility across everything I monitor," "when were my sites last checked or when do they run next," or wants a dashboard of their monitored domains. Returns, per domain, the latest AI-visibility score of its series (the measured weekly re-audits and any audit that asked the same question as the newest recorded one, while it has no gap longer than four weeks and a day from the newest weekly re-audit that recorded its question, through each later snapshot of the series (weekly re-audits included, recorded or not), to the newest measured snapshot; otherwise every measured snapshot; a newer measured snapshot outside the series is not shown, and get_changes names it), the date of its last scheduled run and when the next one runs, and the most recent change against the last snapshot that asked the same question, or a note or the summary saying why there is none; like get_changes, a change carries competitor_changes, new_issues and resolved_issues, always empty. Requires a Website Auditor subscription ($10/month; eligible new customers get a 7-day free trial — payment method required, no charge until the trial ends) — if the user doesn't have one, call get_sample_audit first to show them the exact output format, free and with no API key.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`used`	Yes
`limit`	Yes
`sites`	Yes
`summary`	Yes
`remaining`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.0.24Sep 17, 2026

changedOutput schema / properties / sites / items / properties / change / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {
-      "competitor_changes": {
-        "items": {},
-        "type": "array"
-      },
-      "engine_changes": {
-        "items": {
-          "additionalProperties": true,
-          "properties": {
-            "delta": {
-              "type": "number"
-            },
-            "engine": {
-              "type": "string"
-            },
-            "from": {
-              "type": "number"
-            },
-            "to": {
-              "type": "number"
-            }
-          },
-          "required": [
-            "engine",
-            "from",
-            "to",
-            "delta"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "new_issues": {
-        "items": {},
-        "type": "array"
-      },
-      "resolved_issues": {
-        "items": {},
-        "type": "array"
-      },
-      "score_delta": {
-        "type": "number"
-      }
-    },
-    "required": [
-      "score_delta",
-      "engine_changes",
-      "competitor_changes",
-      "new_issues",
-      "resolved_issues"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "competitor_changes": {
+        "description": "Always empty: AI-visibility snapshots record no competitors. Kept for clients that read it.",
+        "items": {},
+        "type": "array"
+      },
+      "engine_changes": {
+        "items": {
+          "additionalProperties": true,
+          "properties": {
+            "delta": {
+              "type": "number"
+            },
+            "engine": {
+              "type": "string"
+            },
+            "from": {
+              "type": "number"
+            },
+            "to": {
+              "type": "number"
+            }
+          },
+          "required": [
+            "engine",
+            "from",
+            "to",
+            "delta"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "from_captured_at": {
+        "description": "When the earlier snapshot compared was captured.",
+        "type": "string"
+      },
+      "new_issues": {
+        "description": "Always empty: AI-visibility snapshots record no audit issues. Kept for clients that read it.",
+        "items": {},
+        "type": "array"
+      },
+      "resolved_issues": {
+        "description": "Always empty: AI-visibility snapshots record no audit issues. Kept for clients that read it.",
+        "items": {},
+        "type": "array"
+      },
+      "score_delta": {
+        "type": "number"
+      },
+      "skipped_snapshots": {
+        "description": "Snapshots passed over because they asked a different question (another business name, market or queries) or do not record what they asked.",
+        "type": "number"
+      },
+      "to_captured_at": {
+        "description": "When the later one was.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "score_delta",
+      "engine_changes",
+      "competitor_changes",
+      "new_issues",
+      "resolved_issues"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / sites / items / properties / change / description

Previous value: -"Latest vs previous snapshot; null if fewer than two."New value: +"The latest change against the most recent earlier snapshot that asked the same question; null when there is none — no scored latest snapshot (the summary says why), a first snapshot, a re-baseline, or snapshots that do not record what they asked."

addedOutput schema / properties / sites / items / properties / last_audited_at / description

Added value: +"The date of the last scheduled run, stamped when the scheduler claims it and before the audit runs. It does not say how that run ended: it may still be going, or may have failed, been skipped or measured nothing of the business."

addedOutput schema / properties / sites / items / properties / note

Added value: +{
+  "description": "Present when there is no like-for-like change because of a re-baseline or snapshots that do not record what they asked, or when snapshots were passed over: why, in words. Relay it.",
+  "type": "string"
+}

Changed1 schema field changedv1.0.23Sep 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "limit": {
+      "type": "number"
+    },
+    "remaining": {
+      "type": "number"
+    },
+    "sites": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "active": {
+            "type": "boolean"
+          },
+          "cadence": {
+            "type": "string"
+          },
+          "change": {
+            "anyOf": [
+              {
+                "additionalProperties": true,
+                "properties": {
+                  "competitor_changes": {
+                    "items": {},
+                    "type": "array"
+                  },
+                  "engine_changes": {
+                    "items": {
+                      "additionalProperties": true,
+                      "properties": {
+                        "delta": {
+                          "type": "number"
+                        },
+                        "engine": {
+                          "type": "string"
+                        },
+                        "from": {
+                          "type": "number"
+                        },
+                        "to": {
+                          "type": "number"
+                        }
+                      },
+                      "required": [
+                        "engine",
+                        "from",
+                        "to",
+                        "delta"
+                      ],
+                      "type": "object"
+                    },
+                    "type": "array"
+                  },
+                  "new_issues": {
+                    "items": {},
+                    "type": "array"
+                  },
+                  "resolved_issues": {
+                    "items": {},
+                    "type": "array"
+                  },
+                  "score_delta": {
+                    "type": "number"
+                  }
+                },
+                "required": [
+                  "score_delta",
+                  "engine_changes",
+                  "competitor_changes",
+                  "new_issues",
+                  "resolved_issues"
+                ],
+                "type": "object"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Latest vs previous snapshot; null if fewer than two."
+          },
+          "domain": {
+            "type": "string"
+          },
+          "last_audited_at": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "latest_score": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "next_run_at": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "summary": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "domain",
+          "latest_score",
+          "change",
+          "summary"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "summary": {
+      "type": "string"
+    },
+    "used": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "limit",
+    "used",
+    "remaining",
+    "sites",
+    "summary"
+  ],
+  "type": "object"
+}

First observedv1.0.6Jul 29, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds substantial behavioral context: the subscription requirement, the complex series logic for AI-visibility scores, the fact that change fields are always empty, and the fallback to get_sample_audit. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very long and dense, especially the series logic explanation, which is a run-on sentence that is difficult to parse. It is front-loaded with purpose and usage, but the level of detail is excessive for a zero-parameter tool and could confuse agents. The structure is logical but not concise.

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?

The description covers purpose, usage scenarios, return details (per-domain info, series logic, scheduled runs, changes), the subscription requirement, and the fallback to get_sample_audit. An output schema exists, so return values need not be spelled out, but the description still provides enough context for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the schema trivially covers 100%. The description adds no parameter information because none exists, and the baseline for 0 params is 4. No further compensation needed.

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 opens with a clear verb+resource: 'Get a glanceable summary of monitoring status across all tracked websites.' It also lists concrete user queries that should trigger this tool, distinguishing it from siblings like get_changes and get_sample_audit by context and behavior.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use the tool (specific queries) and gives a clear exclusion: if the user lacks a subscription, call get_sample_audit first. It also references get_changes for a related but distinct use case, providing both when-to-use and when-not-to-use guidance.

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

Deploy Server