@dropthis/mcp

Official

by dropthis-dev

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Delete a custom domain

dropthis_domains_delete

Destructive

Disconnect a custom domain: detach its routes so the hostname stops serving drops, while keeping the drops intact. Requires explicit confirmation.

Instructions

Disconnect a custom domain: the hostname stops serving drops and its routes are removed (the drops themselves are NOT deleted). Destructive; requires confirm: true. Afterwards, remove your DNS record for the hostname — while your CNAME still points at dropthis, the hostname could be re-connected by another dropthis account (the response repeats this dangling-CNAME warning with the exact record). If the domain was the publish default, new publishes revert to the shared pool.

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": {
      "domain": "<domain>",
      "confirm": "<confirm>"
    },
    "name": "dropthis_domains_delete"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes	The `dom_…` id or the hostname of the domain to disconnect.
`confirm`	Yes	Must be true to delete.

Output Schema

Name	Required	Description	Default
`id`	No
`deleted`	No
`warning`	No
`hostname`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.37.0Aug 6, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already flag destructiveHint=true, but the description adds substantial behavioral context: the confirm requirement, drops not deleted, the dangling-CNAME security warning, and the fallback to the shared pool if the domain was the publish default. This goes well beyond what annotations provide.

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 well-structured and front-loaded with the core action. Every sentence adds a distinct consequence or instruction—effect, destructive confirmation, DNS warning, and default-publish fallback—with no fluff or repetition.

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 domain-disconnection tool, the description covers all critical outcomes: impact on drops and routes, security warning about DNS, and fallback behavior for the publish default. The presence of an output schema means return values need not be described.

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?

Schema description coverage is 100%, with both parameters fully described ('dom_…' id or hostname, confirm must be true). The description adds no additional parameter-level syntax or format details beyond the schema, so baseline 3 is appropriate.

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+resource ('Disconnect a custom domain') and explains the concrete effect (hostname stops serving drops, routes removed). This clearly differentiates it from sibling tools like connect, verify, update, and list.

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

Usage Guidelines4/5

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

The description gives a clear context for use (disconnecting a domain) and explicitly notes what this tool does NOT do ('the drops themselves are NOT deleted'), providing a when-not signal. It does not name alternative tools, but the guidance is clear.

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