Skip to main content
Glama
SpikeyCoder

Website Auditor MCP

by SpikeyCoder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Monitoring status summary

get_monitoring_status
Read-only

Summarize monitoring status across all tracked websites, showing AI-visibility scores, last/next check times, and recent changes.

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 — when different engines answered the two snapshots, the change shows the per-engine changes only, with a note naming which answered each, and its score_delta is null; 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
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
usedYes
limitYes
sitesYes
summaryYes
remainingYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.25
    • changedOutput schema / properties / sites / items / properties / change / anyOf
      Previous 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"
-  }
-]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"
+      },
+      "overall_note": {
+        "description": "Present exactly when score_delta is null: which engines answered each snapshot. Relay it.",
+        "type": "string"
+      },
+      "resolved_issues": {
+        "description": "Always empty: AI-visibility snapshots record no audit issues. Kept for clients that read it.",
+        "items": {},
+        "type": "array"
+      },
+      "score_delta": {
+        "description": "The overall move, or null when the two snapshots were answered by different engines: the overall is computed over the engines that answered, so an overall over a different set of engines is a different quantity and is not subtracted. `overall_note` says which engines answered each; engine_changes still compares every engine that answered both.",
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "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 / note / description
      Previous value: -"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."New value: +"Present when there is no like-for-like change because of a re-baseline or snapshots that do not record what they asked, when snapshots were passed over, or when the change shown has no overall because different engines answered the two snapshots: why, in words. Relay it."
  2. Changed4 schema fields changedv1.0.24
    • 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"
+}
  3. Changed1 schema field changedv1.0.23
    • 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"
+}
  4. First observedv1.0.6

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only/closed-world/non-destructive, so the description correctly spends its effort elsewhere: it discloses the Website Auditor subscription requirement and trial terms, and describes what the change data contains (per-engine changes, null score_delta, always-empty competitor_changes/new_issues/resolved_issues). The gap is that the deeply convoluted series-inclusion rules are hard to act on, but auth and data-shape context are genuinely additive.

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

Conciseness2/5

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

The purpose and usage examples are front-loaded and useful, but the middle sentence describing the snapshot-series inclusion logic is a single unparseable run-on spanning roughly ten clauses. It is the opposite of glanceable and buries the actionable information.

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

Completeness4/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-value detail is technically redundant, yet the description still enumerates the returned fields and the subscription prerequisite, leaving nothing an agent needs to call it correctly. It is arguably over-complete rather than incomplete for a zero-parameter, output-schema-backed tool.

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 takes zero parameters, so the baseline is 4; the description has no parameters to explain and does not confuse the reader with any.

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?

States a specific verb and resource ('Get a glanceable summary of monitoring status across all tracked websites') and scopes it to monitored domains, distinguishing it from siblings like list_tracked_sites and get_changes, which it even references by name for the out-of-series snapshot case.

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?

Provides explicit trigger phrases ('how are my tracked sites doing', 'what's my current AI visibility', 'when were my sites last checked') and a clear alternative path: if the user lacks a Website Auditor subscription, call get_sample_audit first. When-to-use and fallback behavior are both spelled out.

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

Deploy Server

Other Tools