Skip to main content
Glama

List the folders of a mailbox

list_folders

Lists the folders the people of a mailbox made in it, beside the six every mailbox has (inbox, sent, drafts, spam, trash, archive), each with its id, its name, its full path ("Clients/LCS") and its parent. The ids are what list_conversations, search_conversations and file_conversation take, and what update_folder and delete_folder act on.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "box": "<box>"
    },
    "name": "list_folders"
  }
}

Input Schema

NameRequiredDescriptionDefault
boxYesThe address of the mailbox to look in, for example "simon@sonentreprise.com": call list_sender_addresses to find it. One of its aliases names the same mailbox. A support queue is not a mailbox and has no folders.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / box / description
      Previous value: -"The address of the mailbox to look in, for example \"simon@sonentreprise.com\": call list_sender_addresses to find it. A support queue is not a mailbox and has no folders."New value: +"The address of the mailbox to look in, for example \"simon@sonentreprise.com\": call list_sender_addresses to find it. One of its aliases names the same mailbox. A support queue is not a mailbox and has no folders."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the behavioral burden; it discloses that both system and user-created folders are returned with id, name, full path, and parent. It does not cover permissions, ordering, pagination, or error behavior, leaving some gaps but still providing useful behavioral context.

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 dense sentences with the operation and scope front-loaded. The list of six standard folders and the downstream id usage both earn their place, with no filler.

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?

For a one-parameter read-only listing tool with no output schema, the description supplies the essential return shape and scope. The parameter schema covers address resolution, so an agent has enough information to invoke the tool correctly.

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%, and the only parameter's schema text already explains the mailbox address, aliases, and that support queues are not mailboxes. The description adds no additional parameter-specific detail, so the baseline score of 3 applies.

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 ("Lists") and resource (folders) scoped to a mailbox, including both user-created and six system folders. It names the returned fields and downstream consumers, so it is clearly distinguishable from sibling conversation and folder-mutation tools.

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?

Explicitly links folder ids to list_conversations, search_conversations, file_conversation, update_folder, and delete_folder, giving strong guidance on why an agent would call it. It does not explicitly state when not to use it or contrast with other folder operations such as create_folder, so it falls short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources