Skip to main content
Glama
proton-mail-mcp

proton-mail-mcp

by jasen1300

apply_filters

Apply all sender filters to a mail folder to clean up recurring newsletters, with an optional dry run that previews moves without changing anything.

Instructions

Apply ALL sender filters to a folder (cleanup), e.g. on a schedule against recurring newsletters.

all_mail=True applies to 'All Mail'. dry_run=True only shows what WOULD
happen, without moving anything.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "apply_filters"
  }
}

Input Schema

NameRequiredDescriptionDefault
folderNoINBOX
dry_runNo
all_mailNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two important behaviors: dry_run preview vs. real execution ('without moving anything'), and the all_mail scope switch. It does not say what happens to non-matching mail, whether the operation is reversible, whether filters themselves are consumed or deleted, or what permissions/state are required.

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-loads the core action, then adds the schedule example and parameter notes; no filler sentences. Minor slack: the 'ALL' capitalization and the quoted 'All Mail' could confuse whether all_mail supersedes the folder argument.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value explanation is not needed. However, for an unannotated bulk-mutation tool that moves mail, the description omits safety-relevant details such as reversibility, scope of effect, and error/precondition behavior, leaving the agent under-informed before invoking it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it explains two of three parameters meaningfully: dry_run as a no-op preview and all_mail as targeting 'All Mail'. The folder parameter is only implied by 'apply ... to a folder' and its INBOX default is unmentioned, but the added meaning is substantial for a fully undocumented schema.

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: applying sender filters to a folder, with the '(cleanup)' gloss framing the intent. It is distinguishable from list_filters/create_filter/delete_filter by the verb alone, but it never names a sibling or explicitly contrasts with them.

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?

The parenthetical 'e.g. on a schedule against recurring newsletters' gives an implied usage context. There is no when-not guidance, no stated prerequisite (e.g. filters must exist, use list_filters to verify first), and no mention of how it relates to the sibling filter-management tools.

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