Skip to main content
Glama
googlarz

Proton Mail Bridge MCP

by googlarz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_labels

Read-only

Enumerates Proton folders and labels from the local index with message counts, enabling label selection before filtering emails or threads. Use live folder counts if the index may be stale.

Instructions

Return normalized Proton folders and labels from the local mailbox index, including message counts per label. Use to enumerate available labels before filtering with search_indexed_emails or get_threads. Prefer get_folders for live IMAP folder counts when the index may be stale.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum labels to return. Capped at 250; use get_folders for the complete live folder list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.13.11
  2. Removedv1.13.11
  3. Changed1 schema field changedv1.13.4
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum labels to return."New value: +"Maximum labels to return. Capped at 250; use get_folders for the complete live folder list."
  4. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint true; description adds that it uses local index (potential staleness) and includes message counts, with a limit cap. No contradictions.

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?

Three concise sentences front-loading purpose, usage, and alternative. No wasted words.

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 simple read-only tool with one parameter and no output schema, the description fully covers purpose, behavior, and usage context.

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 covers 100% of the single parameter limit, including cap and alternative suggestion. Description doesn't add new parameter info beyond the schema.

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?

Clearly states it returns normalized Proton folders/labels from local index with counts. Explicitly distinguishes from get_folders for live counts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Directs when to use: before filtering with search_indexed_emails or get_threads. Warns to prefer get_folders for live counts when index may be stale.

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

Deploy Server

Other Tools