OrgLines

Mail: Empty folder

mail_empty_folder

Destructive

Empty a Trash or Spam folder in one go. Refused for any other folder, so an inbox cannot be emptied by this. Removes what the local index knows about and reports the count. There is no undo. CONFIRMATION: this tool is PROPOSED, never performed directly. You get status='confirmation_required' with an action_id and a plan_token, and the write happens only after confirm_action.

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": "mail_empty_folder"
  }
}

Input Schema

Name	Required	Description	Default
`folder`	Yes	A Trash/Spam folder name from mail_list_folders.
`mailbox`	No	Which mailbox (label). Required if you have several.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, yet the description adds substance beyond them: no undo, scope limited to Trash/Spam, only local-index knowledge is removed, and the return reports a count. It also explains the two-step confirmation flow, naming status, action_id, plan_token and confirm_action.

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?

Front-loaded with the action, followed by constraints, outcome and the confirmation protocol, with no filler sentences. The capitalized CONFIRMATION block is a little heavy but every line conveys needed behavior.

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 destructive, confirmation-gated tool with no output schema, the description covers scope, irreversibility, what is affected, result reporting, and the exact status/token handshake needed to finish the operation. Nothing essential to correct invocation 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 coverage is 100%, so both parameters are already documented, and the description only restates the folder constraint already implied. The mailbox parameter is not discussed in the description. Baseline 3 is appropriate when the schema carries the load.

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 concrete verb and resource ('Empty a Trash or Spam folder in one go') and immediately bounds the scope ('Refused for any other folder'). It does not name the sibling mail_empty_folder_except, so the differentiation from the closest alternative is left implicit.

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?

Gives a clear negative condition (any folder other than Trash/Spam is refused, so an inbox cannot be emptied) and explains the confirmation gate. It stops short of pointing to mail_empty_folder_except for the selective variant.

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

All OrgLines tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?