Skip to main content
Glama

delete_folder

Destructive

Deletes an empty Notes folder only when confirmed; refuses folders with notes or subfolders.

Instructions

Delete an empty Notes folder. It is refused when the folder holds any note or any subfolder (the error says how many), for the built-in folders (Notes, Recently Deleted, Quick Notes) and for the default folder or the only folder of an account. It needs 'confirm' true, also for an empty folder. Without it, nothing is deleted. Notes may keep a deleted folder in Recently Deleted for a while.

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": {
      "folder": "<folder>"
    },
    "name": "delete_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
folderYesFolder name (any case) or id.
accountNoAccount name, for example iCloud. Ignores case.
confirmNoMust be true to delete the folder. Without it, nothing is deleted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, and the description adds concrete behavior on top: the refusal rules, that the error reports how many items block deletion, that 'confirm' is mandatory even for an empty folder, and that the folder may linger in Recently Deleted. This is exactly the operational context an agent needs before a destructive call.

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?

Four compact sentences, with the destructive action and its precondition front-loaded and the failure modes and retention note following. A small amount of the confirm wording duplicates the schema, but nothing is wasted at length.

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 three-parameter destructive tool with no output schema, the description covers purpose, refusal conditions, the confirmation gate, and post-deletion behavior. Nothing an agent needs in order to call it safely is missing.

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 all three parameters are already documented, including folder accepting name-or-id and confirm being required. The description restates the confirm requirement and reinforces the empty-folder precondition rather than adding new parameter-level detail, so the 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?

The description opens with a specific verb+resource+precondition: 'Delete an empty Notes folder.' The qualifier 'Notes' and 'empty' separate it from delete_note and the other delete_* siblings without ambiguity.

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?

It enumerates the exact conditions under which the call is refused (non-empty, built-in folders, default/only folder of an account), which effectively tells the agent when not to call it. It does not name an alternative (e.g. listing folders or deleting contents first), so it stops just short of full routing guidance.

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