Skip to main content
Glama
Sign In
privateemail-mcp

privateemail-mcp

by pushkarsingh32
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

list_folders

List mailbox folders with total and unread message counts so you can identify where messages and unread items are stored.

Instructions

List mailbox folders with total and unread message counts.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; "list" implies a safe read, and the mention of per-folder counts is genuine value beyond structured data. However, it is silent on mailbox-wide scope, whether folders are nested, pagination, and cost of fetching counts across many folders.

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 front-loaded sentence with no filler; the returned payload is stated alongside the action instead of buried.

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 trivial zero-param read with no output schema, the description usefully sketches the return shape (folders plus total/unread counts). Minor gap: it doesn't say whether folder identifiers or nesting depth come back, which an agent might need before calling move_messages.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics to compensate for; baseline applies. The schema is an empty object and the description correctly implies there is nothing to supply.

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?

"List mailbox folders" is a specific verb+resource, and it adds what the result contains (total and unread counts). It is obviously distinct from every sibling (send/reply/mark/move/search/read), so no explicit sibling naming is needed, but it doesn't state hierarchy or identifiers returned.

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 only implied: a zero-parameter listing tool is self-evidently a discovery/enumeration entry point, and an agent can infer it feeds folder choices for search_messages or move_messages. The description never says when to use it, nor does it mention any alternative or precondition.

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