drop2run-mcp

Official

by Drop-to-run

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Delete a site

delete_site

Destructive

Permanently delete a site and its subdomain, files, and history; confirm the exact subdomain to prevent mistakes. This action cannot be undone.

Instructions

Takes a site down permanently — its files, its history and its subdomain. Nothing here undoes it, and the subdomain stays reserved — nobody can use it again. Requires confirm to repeat the site's own subdomain exactly; ask the person for it rather than filling it in from what you already know, because that is the step this asks for. To take a site off the air and keep it, use pause_site instead; resume_site brings it back. Only an owner of the account can delete a site; on a team where the person is a member, say an owner has to do it rather than asking them for the subdomain.

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": {
      "site": "<site>",
      "confirm": "<confirm>"
    },
    "name": "delete_site"
  }
}

Input Schema

Name	Required	Description	Default
`site`	Yes	Subdomain or site id to delete.
`confirm`	Yes	The subdomain of the site being deleted, repeated exactly. A mismatch refuses the call rather than guessing which site was meant.

Output Schema

Name	Required	Description	Default
`siteId`	Yes	Identifier of the site that was deleted.
`subdomain`	Yes	Its subdomain, now unclaimed.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.2.1Sep 12, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only flag destructiveHint=true; the description goes well beyond that by stating the operation is irreversible, that the subdomain stays reserved forever, and that a mismatched confirm refuses the call. It also discloses the ownership/permission constraint, which annotations do not cover.

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-loads the consequence ('Takes a site down permanently') before the mechanics, and each sentence carries actionable content. It is dense and slightly long, but there is no filler 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?

Covers the destructive consequence, the confirmation protocol, the ownership constraint, and the alternatives, which is everything an agent needs before calling. An output schema exists, so return values need not be explained.

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?

Schema coverage is 100%, so both parameters are already documented, but the description adds real behavioral meaning to confirm — that the person must supply it rather than the agent inferring it from prior context. That is beyond the schema's 'repeated exactly' wording, though it stops short of extra detail on the site identifier.

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 ('Takes a site down permanently') plus the exact scope of destruction — files, history, subdomain. It also names the sibling it is not (pause_site) and the tool that reverses that alternative (resume_site), so an agent can distinguish it without opening schemas.

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?

Explicit when-not guidance: 'To take a site off the air and keep it, use pause_site instead; resume_site brings it back.' It also names the prerequisite that only an account owner can delete, and tells the agent what to say on a team where the user is merely a member.

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