Skip to main content
Glama
Sign In
DocsMint

DocsMint

by HiAi-gg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

delete_folder

Destructive

Remove a folder while preserving its documents; child folders and documents are detached according to API rules. Requires write access.

Instructions

Delete a folder while preserving its documents; child folders and documents are detached under the API rules. Requires write access.

Input Schema

NameRequiredDescriptionDefault
idYesUUID returned by the corresponding list or read operation.
workspaceIdNoWorkspace UUID from list_workspace_structure(kind=workspaces). Required for ambiguous creates and structure changes; omit to search all granted scopes.

Output Schema

NameRequiredDescriptionDefault
idYes
deletedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.4
    • addedInput schema / properties / workspaceId
      Added value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Workspace UUID from list_workspace_structure(kind=workspaces). Required for ambiguous creates and structure changes; omit to search all granted scopes.",
+  "format": "uuid",
+  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+  "type": "string"
+}
  2. Changed2 schema fields changedv0.1.2
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / id / description
      Previous value: -"UUID of the folder to delete; obtain it from list_folders. This detaches, but does not delete, the documents inside it."New value: +"UUID returned by the corresponding list or read operation."
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered; the description adds the non-obvious side effects (documents survive, children are detached) and the write-access requirement. It stops short of saying whether the folder itself is recoverable via list_trash/restore, which for a destructive tool would be valuable.

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?

One sentence, front-loaded with the action and the critical side effect, with the prerequisite trailing. No waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a full input schema, an output schema, and destructive annotations, the description supplies exactly the missing semantic layer: what survives deletion and what permission is needed. The only gap is recoverability, which an agent planning a destructive call would reasonably want to know.

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%, so both 'id' and the optional 'workspaceId' are already documented in the schema, including their UUID sourcing guidance. The description adds nothing further about parameter values; baseline 3 applies.

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 ('Delete a folder') and immediately disambiguates the outcome from sibling delete tools: documents are preserved while child folders and documents are detached. An agent can distinguish this from delete_document, delete_category, and delete_tag 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 Guidelines3/5

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

'Requires write access' gives a prerequisite, and preserving documents implies when to prefer this over per-document deletion. But there is no explicit when-to-use, when-not-to-use, or named alternative (e.g. list_trash / permanently_delete_document for hard removal).

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