Website Auditor MCP

Stop monitoring

untrack_site

Destructive

Stop ongoing AI-visibility monitoring for a domain to free up a monitoring slot. Safe to call even if the site isn't tracked, and returns the number of slots now available.

Instructions

Stop ongoing monitoring of a website's AI visibility. Use this when someone wants to "stop tracking," "unmonitor," "stop watching," or "remove" a site from scheduled monitoring, or to free up a monitoring slot. Idempotent — safe to call even if the site isn't currently tracked. Returns how many monitoring slots are now free. 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
`domain`	Yes	The website domain, e.g. "example.com".

Output Schema

TableJSON Schema

Name	Required	Description	Default
`used`	No
`limit`	No
`domain`	Yes
`message`	Yes
`removed`	Yes
`tracking`	Yes
`remaining`	No

Schema Changelog

Changes observed during successful MCP inspections.

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": {
+    "domain": {
+      "type": "string"
+    },
+    "limit": {
+      "type": "number"
+    },
+    "message": {
+      "type": "string"
+    },
+    "remaining": {
+      "type": "number"
+    },
+    "removed": {
+      "type": "boolean"
+    },
+    "tracking": {
+      "type": "boolean"
+    },
+    "used": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "domain",
+    "tracking",
+    "removed",
+    "message"
+  ],
+  "type": "object"
+}

First observedv1.0.6Jul 29, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already flag destructiveHint=true, and the description builds on that by disclosing idempotence, the return value (number of slots freed), and the subscription prerequisite. It also explains the fallback behavior for users without a subscription, which is valuable beyond the structured annotations.

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

Conciseness4/5

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

The description is longer than average, but every sentence contributes: purpose, trigger phrases, idempotence, return value, subscription prerequisite, and alternative tool. The main action is front-loaded, and only the subscription/trial detail adds mild verbosity.

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?

For a destructive, paid-gated tool, the description covers when to use it, what to tell the user about subscription, what happens if the site is not currently tracked, and what the result will be. An output schema exists and the description also mentions the return value, so no critical context is missing.

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?

The input schema has 100% coverage for the single required parameter, domain, with a clear example. The description does not add much domain-specific semantic detail beyond the schema, but none is needed given the schema's completeness.

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 specific verb and resource: "Stop ongoing monitoring of a website's AI visibility." It distinguishes itself from siblings like track_site and list_tracked_sites by clearly stating the reverse operation, and it provides natural-language triggers for when a user wants this action.

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 says when to use the tool (“stop tracking,” “unmonitor,” “stop watching,” “remove” a site, free a slot) and provides an explicit alternative path: call get_sample_audit first if the user lacks a subscription. This is strong routing guidance.

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

Deploy Server