Skip to main content
Glama
Sign In
Commonpost MCP for Thunderbird

Commonpost MCP for Thunderbird

by commonpost
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
JavaScript
Local

List Folders

listFolders
Read-onlyIdempotent

Lists Thunderbird mail folders with paths, types, account IDs, message and unread counts, depth, and favorite status so you can find the folderPath needed for message searches or refreshes.

Instructions

List mail folders, flat: name, path (the URI every folderPath takes), type (inbox, sent, drafts, trash, junk...), accountId, total and unread counts, depth, isFavorite. Use it to find a folderPath; messages: searchMessages or getRecentMessages. refresh (with folderPath) first fetches new mail from the server, up to 20 s.

Input Schema

NameRequiredDescriptionDefault
formatNo'objects' (default) or 'table' ({ columns, rows }, compact)
refreshNoWith folderPath: first fetch its new mail from the mail server (waits up to 20 s); returns { refresh, folders }
accountIdNoAccount ID (from listAccounts): only its folders
folderPathNoFolder URI: only that folder and its subfolders
favoritesOnlyNoOnly the folders the user marked as favorites
savedSearchesNoIf true, return only saved searches (virtual folders) with their folders and conditions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.19.2
    • changedInput schema / properties / accountId / description
      Previous value: -"Optional account ID (from listAccounts) to limit results to a single account"New value: +"Account ID (from listAccounts): only its folders"
    • changedInput schema / properties / favoritesOnly / description
      Previous value: -"If true, return only folders the user has marked as favorites in Thunderbird (default: false)"New value: +"Only the folders the user marked as favorites"
    • changedInput schema / properties / folderPath / description
      Previous value: -"Optional folder URI (from listFolders) to list only that folder and its subfolders"New value: +"Folder URI: only that folder and its subfolders"
    • removedInput schema / required
      Removed value: -[]
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

The annotations already establish read-only, idempotent, non-destructive behavior, and the description adds detail beyond them: refresh fetches new mail first, waits up to 20 seconds, returns { refresh, folders }, and the listing is flat. Those are meaningful behavioral and output-shape details an agent would not get from the annotations alone.

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?

The description is dense but front-loaded and every clause carries information: output fields, routing guidance, and refresh behavior. There is no filler and the semicolon-separated structure keeps the key usage rule easy to find.

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?

With no output schema, the description compensates by naming the returned fields and explaining the refresh return shape. Combined with annotations covering safety and a fully documented schema, it gives an agent enough context to call the tool correctly.

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 coverage is 100%, so the baseline is 3, but the description adds useful connections: the returned path is the URI that folderPath accepts, and refresh is only meaningful with folderPath. It also gives examples for the folder type field, though most parameter details are already in 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?

The description gives a specific verb and resource (list mail folders), states the flat output shape, and enumerates the returned fields (name, path, type, accountId, counts, depth, isFavorite). It also explicitly distinguishes the tool from message-reading siblings by naming searchMessages and getRecentMessages.

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 states the primary use case: find a folderPath. It also routes message retrieval to searchMessages or getRecentMessages, and explains that refresh must be combined with folderPath. This gives explicit when-to-use guidance and clear alternatives for a common adjacent task.

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