Skip to main content
Glama

Remove Monitored Website

delete_website
DestructiveIdempotent

Remove a website from monitoring so the site and its keywords stop matching new mentions and free up plan slots. Permanently deletes the record; use disable_keyword instead to pause a single keyword.

Instructions

Remove a website from monitoring. This is a soft delete: the site and its keywords leave list_websites immediately and stop matching new mentions. Its active keywords free plan slots, so the oldest pending keywords on other websites that now fit may become active, which queues public-network searches and ranking checks. 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 to erase one keyword and its mentions. 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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "websiteId": "<websiteId>"
    },
    "name": "delete_website"
  }
}

Input Schema

NameRequiredDescriptionDefault
websiteIdYesID of the website to delete, from list_websites or the id create_website returned. Check its domain there before deleting
workspaceIdNoWorkspace to act in: an id from list_workspaces. Omit to use the default workspace. Use the same workspaceId for every call about the same workspace, since ids from one workspace do not exist in another

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv1.6.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / websiteId / description
      Previous value: -"Monitored website ID (UUID)"New value: +"ID of the website to delete, from list_websites or the id create_website returned. Check its domain there before deleting"
    • addedInput schema / properties / websiteId / format
      Added value: +"uuid"
    • addedInput schema / properties / workspaceId
      Added value: +{
      +  "description": "Workspace to act in: an id from list_workspaces. Omit to use the default workspace. Use the same workspaceId for every call about the same workspace, since ids from one workspace do not exist in another",
      +  "type": "string"
      +}
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedOutput schema / properties / result / additionalProperties
      Added value: +true
    • removedOutput schema / properties / result / description
      Removed value: -"{ deleted: true } once the website is soft-deleted."
    • addedOutput schema / properties / result / properties
      Added value: +{
      +  "deleted": {
      +    "description": "Always true on success; a failed delete returns an error instead",
      +    "type": "boolean"
      +  }
      +}
    • addedOutput schema / properties / result / required
      Added value: +[
      +  "deleted"
      +]
    • addedOutput schema / properties / result / type
      Added value: +"object"
    • addedOutput schema / required
      Added value: +[
      +  "result"
      +]
  2. Changed1 schema field changedv0.1.1
    • changedOutput schema / properties / result / description
      Previous value: -"Confirmation that the website was deleted."New value: +"{ deleted: true } once the website is soft-deleted."
  3. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already flag destructiveHint and idempotentHint, and the description adds real substance beyond them: soft delete semantics, immediate removal from list_websites, cessation of new mention matching, the keyword slot cascade that can activate pending keywords elsewhere and queue searches, no restore tool, revival via create_website with the same URL, and the 404 condition. This is exactly the side-effect disclosure a destructive operation needs.

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?

Front-loaded with the action and the soft-delete nature, then side effects, then alternatives, then confirmation. Dense but every clause carries distinct operational information; the keyword-slot cascade is the longest stretch but is genuinely load-bearing for a destructive call.

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?

An output schema exists, yet the description still states the concrete return shape and the 404 failure case. Combined with workspace guidance in the schema and full side-effect disclosure, nothing an agent needs before calling is missing.

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

Parameters5/5

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

Schema coverage is 100% and already documents both parameters, so the baseline would be 3. The description nonetheless adds operational meaning: identify the target by domain rather than raw ID and say the domain back to the user, which is a validation step the schema does not require.

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?

Opens with a specific verb and resource ('Remove a website from monitoring') and immediately narrows it with the soft-delete qualifier. It clearly separates itself from the keyword-level siblings, so an agent can choose it without opening any schema.

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 scopes use to 'when the whole site should go' and names the two alternatives with their distinct conditions (disable_keyword to pause and keep the site, delete_keyword to erase one keyword). It also prescribes a confirmation step, so both when-to-use and when-not-to-use are present.

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