Skip to main content
Glama

Delete a folder

delete_folder

Deletes a folder a person made and the folders under it. Their threads go to the Trash, where they stay readable and restorable for 30 days by default, or for the retention set on the account; nothing is deleted for good. The answer says how many went there.

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_id": "<folder_id>"
    },
    "name": "delete_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
folder_idYesThe folder, by its id from list_folders.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does so well: it discloses the soft-delete semantics (threads go to Trash), the retention window (30 days by default, or account-configured), restorability, and that nothing is permanently deleted. What it omits is permission/ownership requirements for performing the deletion.

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?

Three short sentences, front-loaded with the destructive action and its scope, then the recovery model, then the return summary. Only mild informality ('a person made', 'how many went there') costs it a point; nothing is redundant.

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 single-parameter destructive tool with no output schema and no annotations, the description covers scope, reversibility, retention, and return value - the points an agent most needs before invoking a delete. Only authorization preconditions are 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 coverage is 100% and the single folder_id parameter is already documented with its origin (list_folders). The description adds no further detail on the id format or how to obtain it, so the baseline of 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 (deletes) plus resource (a folder) and, crucially, the recursive scope ('and the folders under it'), which distinguishes it from conversation- or note-level delete siblings without naming them. An agent can tell exactly what this removes.

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 by the name and description - use it to remove a folder tree - but there is no explicit when-to-use/when-not guidance, no mention of required permissions or ownership, and no note on what happens if the folder is already empty or shared. The agent must infer the preconditions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources