Skip to main content
Glama

list_mailboxes

Read-only

Lists mailboxes with paths and unread counts for all accounts or one specified account, and shows Gmail labels as mailboxes.

Instructions

List mailboxes with their path and unread count, for all accounts or one. Gmail labels show as mailboxes.

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_mailboxes"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoAccount id or name. Default: all accounts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description's extra burden is light. It nonetheless adds real behavioral context beyond the structured fields: the result carries path and unread count, and Gmail labels are surfaced as mailboxes, which prevents a common misinterpretation.

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 tight sentence with the scope and the returned fields front-loaded. Every clause carries information; nothing is redundant or padded.

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, zero-required-param listing tool with full schema coverage and annotations, this is nearly complete: it names the returned fields and the Gmail label mapping. The only gap is the relationship to the folders/accounts listing tools, which an agent may still have to guess.

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 coverage is 100% and the single parameter already documents 'Account id or name. Default: all accounts.' The description restates the same all-versus-one scope without adding format or resolution details, so it does not meaningfully extend the schema.

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?

Specific verb plus resource: 'List mailboxes' with the returned fields named (path and unread count) and the scope stated ('all accounts or one'). It doesn't explicitly distinguish itself from the sibling list_folders, which is the main ambiguity an agent would face, but the mailbox/label framing helps.

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?

Usage is implied rather than stated: the agent can infer this is the discovery call before acting on messages, and that omitting the account param widens scope. There is no explicit when-to-use, when-not-to-use, or named alternative such as list_folders.

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