Skip to main content
Glama

imap_list_mailboxes

Read-onlyIdempotent

List IMAP mailboxes for a specified account to inspect available folders and target the right mailbox.

Instructions

List mailboxes for an account

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

Input Schema

NameRequiredDescriptionDefault
account_idNoAccount identifier (defaults to `"default"`)default

Output Schema

NameRequiredDescriptionDefault
dataYesTool-specific data payload
metaYesExecution metadata (timestamp, duration)
summaryYesHuman-readable summary of the operation outcome

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.12

TDQS

C2.9/5.0
Behavior2/5

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

The annotations already state readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds nothing about behavior: scope (all mailboxes versus only subscribed ones), whether the result is flat or hierarchical, or what happens for an unknown account_id. No annotation contradiction.

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

Conciseness3/5

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

The description is a single six-word sentence with no filler, so it is maximally concise. It is too terse, however: every sentence earns its place only because there is so little to say.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple: zero required parameters, a fully documented schema, an output schema, and annotations that carry the safety hints. The minimum needed to call it correctly is present. The description still omits what the returned mailbox list represents and how to choose between this tool and the search siblings.

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?

There is one parameter and schema coverage is 100%. The schema already documents account_id, its default of 'default', and the fact that it is shared across three tools. The description adds nothing beyond that, which is the baseline 3 case.

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 states a specific verb and resource: 'List mailboxes for an account'. That is enough for an agent to know it enumerates mailboxes rather than messages. However, it does not distinguish it from siblings such as imap_search_all_mailboxes or imap_mailbox_status, so the agent must open those definitions to choose between them.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. The agent is not told, for example, that this lists mailbox folders rather than searching their contents.

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