Skip to main content
Glama

Delete folder

delete_folder
Destructive

Delete an Outlook mail folder and all messages inside it. Moves the folder to Deleted Items by default, or permanently removes it when requested; built-in folders are protected.

Instructions

Delete a folder and everything in it. By default it is moved to Deleted Items; built-in folders cannot be deleted.

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 to delete. Accepts a well-known name (inbox, drafts, sentitems/sent, deleteditems/trash, junkemail/junk, archive, outbox), a display name or path such as "Inbox/Projects", or a folder ID from list_folders
permanentNoPermanently delete instead of moving to Deleted Items (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description earns credit for adding what those flags cannot — that the deletion cascades to all contained items, that the default is a recoverable move to Deleted Items, and that built-in folders are protected. It stops short of covering permission requirements or whether children follow the folder into Deleted Items under the permanent flag.

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?

Two short sentences, no filler, and the destructive scope ('everything in it') is front-loaded before the recovery and restriction caveats.

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?

For a two-parameter destructive tool with full schema coverage and no output schema, the definition covers cascade scope, recoverability, and protection of built-in folders — everything needed to invoke it safely. Only permission/auth expectations and post-permanent-delete recoverability are left unstated.

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 parameters, including accepted folder name formats and the permanent flag default, are fully documented in the schema. The description adds only the built-in-folder restriction on the folder argument, which is a genuine constraint beyond the schema, but the rest is repetition of the schema's default-behavior note.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 adds the important scope detail 'and everything in it', which distinguishes it from delete_messages or delete_event that act on contents rather than containers. It does not name a sibling alternative for moving/renaming folders, but the resource noun is unambiguous.

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?

Usage is implied rather than stated: the description tells the agent that built-in folders cannot be deleted but offers no explicit when-to-use framing or pointer to alternatives such as move_folder or list_folders for discovery. The default soft-delete behavior implicitly tells an agent this is the normal delete path, which is useful but not spelled out.

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