Skip to main content
Glama
googlarz

Proton Mail Bridge MCP

by googlarz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_drafts

Read-only

Review locally saved Proton Mail drafts by status, subject, and timestamps, with attachment metadata and body previews. Use get_draft for full content, or list_remote_drafts for server-only drafts.

Instructions

List all locally saved drafts with their status, subject, and timestamps. Attachment content is omitted here (filename/type/size only) — use get_draft for the full attachment content of one draft. Each draft's body is also truncated to a short preview (bodyTruncated:true, bodyLength gives the real size) — use get_draft for the full body of one draft. Use to review in-progress or unsent messages. Does NOT list drafts stored only on the Proton server — use list_remote_drafts for those. Prefer get_draft when you already have a draftId and need the full content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum drafts to return. Defaults to 20; check hasMore and page with offset for more.
offsetNoNumber of drafts to skip, newest-updated first.
includeSentNoInclude drafts already sent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.37
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Maximum drafts to return. Defaults to 20; check hasMore and page with offset for more.",
+  "type": "number"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Number of drafts to skip, newest-updated first.",
+  "type": "number"
+}
  2. Addedv1.13.11
  3. Removedv1.13.11
  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?

Beyond the readOnlyHint annotation, the description reveals important behaviors: attachment content is omitted (only filename/type/size), body is truncated to a preview with bodyTruncated:true and bodyLength indicating real size, and it only lists local drafts. It also directs users to get_draft for full content, giving a complete picture of limitations.

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?

Every sentence in the description earns its place, with the main function front-loaded and supporting details (omissions, alternatives) following. It is slightly long, but each sentence adds critical usage information, making the description highly efficient.

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?

The description tells the agent exactly what fields will be returned (status, subject, timestamps), what is omitted (attachment content, full body), how to identify truncation (bodyTruncated), and which alternatives to use for full content or server-only drafts. Combined with the schema, no critical context is missing for correct invocation.

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?

The schema already covers all three parameters (limit, offset, includeSent) with descriptions at 100% coverage rates. The tool description does not add significant extra parameter semantics, but it also does not need to because the schema is sufficient.

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?

The description uses a specific verb and resource: 'List all locally saved drafts with their status, subject, and timestamps.' It explicitly distinguishes this tool from get_draft and list_remote_drafts, so an agent can immediately know what it does and what it does not do.

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?

The description provides explicit when-to-use and when-not-to-use guidance: 'Use to review in-progress or unsent messages,' 'Does NOT list drafts stored only on the Proton server — use list_remote_drafts,' and 'Prefer get_draft when you already have a draftId and need the full content.' This makes the choice among sibling tools clear.

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