Skip to main content
Glama

List Mail Folders

list_mail_folders
Read-only

List top-level mail folders with item and unread counts to identify valid destinations before moving messages.

Instructions

List mail folders with item and unread counts, for resolving move destinations. Top-level folders only — a folder reporting subfolders has children this does not list.

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

Input Schema

NameRequiredDescriptionDefault
mailboxNoEmail address of another mailbox to act on (delegated or shared), e.g. 'someone@example.com'. Omit for your own mailbox; required when this server signs in as an application. Only addresses this server is configured to allow will be accepted.
fetch_all_pagesNoFetch all pages of results (max 50 pages)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds genuine behavioral detail: returned counts and the top-level-only limitation with the subfolder caveat. It does not mention pagination behavior, despite a fetch_all_pages parameter existing.

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 tight sentences: capability and purpose first, limitation second. Every clause carries information; no filler or restatement of the title.

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 simple read-only two-parameter list tool with full schema coverage, the description covers purpose, returned metadata, and the key scope limitation. The only notable omission is how pagination interacts with the top-level folder results, which the schema's fetch_all_pages hints at but the description never connects.

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 both mailbox and fetch_all_pages are already documented. The description adds no new meaning about how parameters affect scope or results, which is the expected baseline when the schema carries the load.

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?

States a specific verb and resource ('List mail folders') and immediately adds what the listing contains (item and unread counts) and why it exists ('for resolving move destinations'). An agent can tell this is a folder-enumeration tool for choosing move targets, distinct from message-listing siblings like list_messages.

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

Usage Guidelines4/5

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

The clause 'for resolving move destinations' tells the agent the intended use case, and the caveat about top-level-only results tells it when the output is insufficient. It stops short of naming an alternative tool for enumerating subfolders, so the when-not guidance is implied rather than fully routed.

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