redreplier

Stop Monitoring Website

delete_website

Destructive

Stop monitoring a website and its keywords, removing them from your active list immediately. Use when the entire site should no longer be tracked; re-add the URL later with create_website if needed.

Instructions

Stop monitoring a website (soft delete). The site and its keywords leave list_websites immediately and stop matching new mentions; there is no restore tool, but create_website with the same URL revives the record. Use this only when the whole site should go: use disable_keyword to pause one keyword and keep the site, and delete_keyword for a PENDING keyword you never want. Confirm with the user first and name the domain, not just the ID. Returns { deleted: true }; 404 if the ID is unknown to this account.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`websiteId`	Yes	Monitored website ID (UUID)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	No	{ deleted: true } once the website is soft-deleted.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.1Sep 7, 2026

changedOutput schema / properties / result / description

Previous value: -"Confirmation that the website was deleted."New value: +"{ deleted: true } once the website is soft-deleted."

First observedv0.1.0Sep 7, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description details the full behavioral impact: immediate removal from list_websites, cessation of matching new mentions, irreversibility (no restore tool), and the exact response format including the 404 error case. This goes far beyond the annotations (destructiveHint) to set complete expectations.

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

Conciseness5/5

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

The description is concise and every sentence carries meaningful information. It efficiently packs purpose, usage guidance, behavioral consequences, and error handling without redundancy or unnecessary detail.

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?

Covers all necessary context: what happens, when to use, what not to use, irreversibility, and return/error behavior. The presence of an output schema further complements the description, yet the description already covers the key aspects thoroughly.

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 description does not add further meaning to the websiteId parameter beyond the schema's own description ('Monitored website ID (UUID)'). Since schema coverage is 100% and the parameter is self-explanatory, the baseline score of 3 applies.

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 clearly states the tool's action ('Stop monitoring a website (soft delete)') and specifies the resource (website). It also distinguishes it from related sibling tools like disable_keyword and delete_keyword, making its purpose unambiguous.

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?

Explicitly states when to use the tool ('Use this only when the whole site should go') and contrasts it with alternatives (disable_keyword, delete_keyword), including the instruction to confirm with the user first. This provides clear guidance on when to select this tool over others.

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