Skip to main content
Glama
Sign In
@dropthis/mcp

@dropthis/mcp

Official
by dropthis-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete a drop

dropthis_delete
Destructive

Permanently delete a drop and its public URL by specifying its drop_id. Requires explicit confirmation to prevent accidental removal.

Instructions

Permanently delete a drop and its public URL by drop_id (the drop_… id, not the slug or URL). Destructive and irreversible; requires confirm: true.

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": {
      "drop_id": "<drop_id>",
      "confirm": "<confirm>"
    },
    "name": "dropthis_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true to delete.
drop_idYesThe `drop_…` id of the drop to delete (id-only — a URL or slug is rejected; call dropthis_resolve to turn a public URL/slug into its id first).

Output Schema

NameRequiredDescriptionDefault
dropIdNo
deletedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.37.0

TDQS

A4.5/5.0
Behavior5/5

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

The description goes beyond the destructiveHint annotation by specifying that both the drop and its public URL are removed, the operation is irreversible, and a confirmation flag is mandatory. This is critical behavioral context for an agent evaluating the consequences of invoking the tool.

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 a single, well-structured sentence that front-loads the core action and packs in the identifier constraint, destructiveness, and confirmation requirement without any wasted words.

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 two-parameter destructive tool with an output schema, the description covers the essential aspects: the action, the identifier specificity, the irreversibility, and the required confirmation. No critical information is missing for an agent to decide on and execute the tool correctly.

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%, and the schema already thoroughly documents both parameters, including the drop_id format and the confirm constraint. The main description reiterates these points but does not add new parameter-level meaning beyond the schema, so a baseline of 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 clearly states the tool's purpose: to permanently delete a drop and its public URL using a drop_id. It specifies the exact identifier type ('drop_…' id, not slug or URL), distinguishing it from workspace deletion and other sibling tools.

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 provides clear context: use this tool for permanent deletion of a drop, emphasizing that it is destructive and irreversible and requires confirm=true. It does not explicitly list alternatives or when-not-to-use scenarios, but the context is unambiguous.

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

Deploy Server

Other Tools