Skip to main content
Glama
second-brain-imap

second-brain-imap

Mail List Folders

mail_list_folders
Read-only

List IMAP mailboxes, folders, and labels with message and unread counts so you can inspect mailbox structure and spot unread activity without modifying the account.

Instructions

List the mailboxes (folders and labels) with their message and unread counts.

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": "mail_list_folders"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that counts accompany each mailbox and that labels as well as folders are included, but says nothing about hierarchy, system folders, or result ordering — context the output schema partly absorbs.

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?

A single front-loaded sentence with the resource and the returned data in the first clause and zero filler. Nothing could be removed without losing meaning.

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 no-parameter read tool with an output schema and read-only annotations, the description covers what is enumerated and what comes back. Only minor gaps remain, such as whether nested folders are flattened, which an agent could reasonably want to know.

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?

The tool takes zero parameters, which is the baseline-4 case; there is no parameter meaning left for the description to supply. The description correctly implies an unfiltered, whole-account listing rather than misrepresenting any input.

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?

The description pairs the verb "List" with a specific resource, "mailboxes (folders and labels)", and even disambiguates provider terminology by equating mailboxes with folders and labels. It is unambiguous on its own; it simply does not name or contrast the sibling tools (mail_read, mail_recent, mail_search), so it earns a 4 rather than a 5.

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?

There is no explicit when-to-use or when-not-to-use guidance. Usage is only implied: an agent can infer this is the discovery step before reading or searching mail, but the description never says that or points at the alternatives.

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