Skip to main content
Glama
owlpost

owlpost

list_folders

Read-onlyIdempotent

Lists every IMAP mailbox in an account, returning folder names, flags, hierarchy delimiter, and detected role for use in other email tools.

Instructions

List every IMAP folder (mailbox) in an account.

Each entry has the folder name to use in other tools, its raw IMAP flags, the hierarchy delimiter, and a detected role (inbox, sent, trash, drafts, junk, archive, all, flagged, important) based on RFC 6154 SPECIAL-USE flags, or null for ordinary folders.

Args: account: Account name from list_accounts.

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": {
      "account": "<account>"
    },
    "name": "list_folders"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.3.0
    • addedOutput schema / $defs
      Added value: +{
      +  "Folder": {
      +    "properties": {
      +      "delimiter": {
      +        "title": "Delimiter",
      +        "type": "string"
      +      },
      +      "flags": {
      +        "title": "Flags",
      +        "type": "string"
      +      },
      +      "name": {
      +        "title": "Name",
      +        "type": "string"
      +      },
      +      "role": {
      +        "anyOf": [
      +          {
      +            "type": "string"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "title": "Role"
      +      }
      +    },
      +    "required": [
      +      "name",
      +      "flags",
      +      "delimiter",
      +      "role"
      +    ],
      +    "title": "Folder",
      +    "type": "object"
      +  }
      +}
    • addedOutput schema / properties / result / items / $ref
      Added value: +"#/$defs/Folder"
    • removedOutput schema / properties / result / items / additionalProperties
      Removed value: -true
    • removedOutput schema / properties / result / items / type
      Removed value: -"object"
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value by explaining how the folder `role` is derived (RFC 6154 SPECIAL-USE flags) and that it is null for ordinary folders, which is behavior an agent could not infer from annotations or the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The first sentence front-loads the purpose, and the entry-format paragraph is dense with useful detail. The 'Args:' block for a single parameter is slightly formal overhead but earns its place by naming the sibling source of the value.

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?

With one required parameter, a full annotation set and an output schema, the description covers what is needed: the source of the account argument and the shape/meaning of the returned folder metadata. It stops short of mentioning failure modes (bad account name, auth errors) that would make it fully self-sufficient.

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 0%, so the description must carry the full burden for the single `account` parameter. It does clarify the expected value as an 'Account name from list_accounts', which identifies both the source and the format, but no further constraints (casing, aliasing) are given.

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?

States a specific verb and resource: list every IMAP folder (mailbox) in an account, with 'mailbox' disambiguating the term. It does not distinguish itself from the sibling resolve_folder, which plausibly overlaps in purpose, so it falls short of 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?

Implies intended usage by noting the returned folder `name` is what you pass to other tools, establishing this as an entry-point/discovery call, and it points at list_accounts for the required argument. It gives no explicit when-to-use versus when-not-to-use guidance, and never contrasts with resolve_folder.

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