Skip to main content
Glama
Sign In
KevinChu1110

driftnet

by KevinChu1110
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete a folder

driftnet_delete_folder
Destructive

Delete a folder while preserving its contents: move items and subfolders up to the parent or 'other' instead of erasing them.

Instructions

Delete one folder. Nothing inside is lost: its items and sub-folders move up to its parent, or to "other" at the top level. Only do it when the reader asked; to empty a folder without deleting it move its items with driftnet_move_items, and to rename it use driftnet_update_folder. Ids are stable lowercase slugs (e.g. 'games', or a generated 'f-…' id for names without Latin letters) that don't change on rename; sub-folders keep their own ids when they move up; "other" is the catch-all and can't be deleted. No tool can undo it, so confirm with the reader first. Fails if the folder does not exist.

Input Schema

NameRequiredDescriptionDefault
idYesFolder id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.0
    • changedInput schema / properties / id / description
      Previous value: -"Folder id from driftnet_list_folders, e.g. 'games'; not 'other'"New value: +"Folder id"
  2. Changed3 schema fields changedv0.7.0
    • changedInput schema / properties / id / description
      Previous value: -"Folder id from driftnet_list_folders"New value: +"Folder id from driftnet_list_folders, e.g. 'games'; not 'other'"
    • addedInput schema / properties / id / maxLength
      Added value: +80
    • addedInput schema / properties / id / minLength
      Added value: +1
  3. Addedv0.5.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and non-idempotent, so the bar is lower, yet the description adds material behavior beyond them: contents survive and move to the parent or the top-level 'other' bucket, sub-folders retain their ids, 'other' is undeletable, the action is not undoable, and it fails on a missing folder. That is precisely the pre-call risk information an agent needs for an irreversible mutation.

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 verb, resource, and non-destructive semantics; every sentence carries operational content. The mid-paragraph id-slug clause is somewhat dense and is likely repeated across sibling folder tools, which slightly dilutes focus for a single-parameter delete.

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 one-parameter destructive tool with full annotations and no output schema, the description covers reparenting consequences, protected folders, irreversibility, confirmation, and the failure mode. Nothing an agent needs before calling is absent.

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 the schema only says 'Folder id', so the description carries real added meaning: ids are stable lowercase slugs, examples are given ('games', generated 'f-…' for non-Latin names), ids survive renames, and moved sub-folders keep their own ids. This directly helps an agent supply the correct identifier rather than guessing.

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 ('Delete one folder') and immediately defines the scope of the operation: children are not deleted but reparented. It is unambiguously distinguishable from driftnet_delete_item and driftnet_update_folder, which are named in the same paragraph.

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-to-use constraint ('Only do it when the reader asked') plus two named alternatives with the condition that selects each: driftnet_move_items to empty a folder without deleting, driftnet_update_folder to rename. It also adds a confirmation prerequisite ('confirm with the reader first'), leaving nothing to inference.

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