Skip to main content
Glama

Delete a folder

delete_folder
DestructiveIdempotent

Use this when the user wants a folder removed. Its lists are kept and end up in no folder. It cannot be restored. Free.

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

Input Schema

NameRequiredDescriptionDefault
folderIdYesThe folder's id.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description adds real value on top: child lists survive and become unparented, and the action is irreversible. The trailing "Free" hints at a cost/quota exemption but is too terse to be actionable, which keeps it off a 5.

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 short sentences, front-loaded with the activation condition and followed by consequences in order of importance (data retention, then irreversibility). The fragment "Free." is cryptic enough to read as noise rather than information.

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, the description covers the trigger, the child-object outcome, and irreversibility, which is what an agent needs before calling. It omits any confirmation or post-delete return behavior, a minor gap given the simplicity.

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% (folderId documents itself with a 24-hex pattern and length bounds), so the schema carries the parameter semantics. The description adds no format or sourcing guidance for folderId beyond what the schema provides, making baseline 3 appropriate.

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 ("folder removed") and immediately clarifies the folder/list relationship with "Its lists are kept and end up in no folder," which disambiguates it from delete_list-style siblings. It stops short of naming a sibling outright, so it is clear but not maximally differentiated.

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?

"Use this when the user wants a folder removed" gives an explicit trigger condition, which is stronger than implied usage. There is no when-not guidance or pointer to an alternative (e.g. delete_list for removing the contents), so it does not reach the top band.

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