Commonpost MCP for Thunderbird

Get Recent Messages

getRecentMessages

Read-onlyIdempotent

Fetches recent messages newest-first from all accounts' folders or one folder, with unread, flagged, and date filters; use it to review incoming mail without a search query.

Instructions

Recent messages newest-first from all folders of all accounts (Trash/Junk skipped) or from one folder, with no query. Same envelope and row format as searchMessages; to filter by words, sender or dates, use searchMessages.

Input Schema

Name	Required	Description
`fields`	No	Only these row columns (id, folderPath and option columns always); not with countOnly, groupBy or legacy
`format`	No	'table' returns messages as { columns, rows }. 'legacy' (deprecated): the 0.10 output, as in searchMessages
`offset`	No	Rows to skip; use with hasMore
`daysBack`	No	Only messages from the last N days
`folderPath`	No	Folder URI (from listFolders); omit for all folders
`maxResults`	No	Rows per page
`unreadOnly`	No	Only unread
`flaggedOnly`	No	Only flagged/starred
`includeTrash`	No	Also include Trash and Junk
`includeSubfolders`	No	Include subfolders of folderPath

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.19.2Nov 5, 2026

addedInput schema / properties / fields

Added value: +{
+  "description": "Only these row columns (id, folderPath and option columns always); not with countOnly, groupBy or legacy",
+  "items": {
+    "enum": [
+      "date",
+      "author",
+      "recipients",
+      "ccList",
+      "subject",
+      "read",
+      "flagged",
+      "tags",
+      "preview",
+      "dupLocations"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

removedInput schema / required
```
Removed value: -[]
```

First observedv0.1.0Nov 5, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the bar is lower. The description still adds real context beyond them: Trash and Junk are skipped unless included, results come newest-first, and the response envelope matches searchMessages. It does not mention pagination or hasMore explicitly, which keeps it from 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with zero waste; the scope and ordering are front-loaded, and the sibling routing follows immediately. Nothing is repeated or padding.

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 ten-parameter read tool with no output schema, the description supplies the important context: default Trash/Junk exclusion, ordering, folder scoping, and a pointer to searchMessages for the row/envelope format. Only pagination behavior is left implicit, a minor gap.

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%, so every one of the ten parameters is already documented in the schema. The description only reinforces the folder scope and the Trash/Junk exclusion default, adding little syntax or constraint detail beyond what the schema provides; baseline 3 is correct.

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 ('Recent messages newest-first from all folders of all accounts ... or from one folder') and immediately distinguishes itself from searchMessages by stating it runs 'with no query'. An agent can tell exactly what this tool returns and how it differs from the query-based sibling.

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?

It gives an explicit selection rule: use this tool for unfiltered recency, and 'to filter by words, sender or dates, use searchMessages.' That names the alternative and the condition that selects it, leaving nothing to inference.

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

Get Recent Messages

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools