Skip to main content
Glama

list_emails

Read-only

Retrieve recent emails from a Proton Mail folder, newest first, with options to set the limit, choose a folder, and filter unread messages only.

Instructions

List the most recent emails of a folder, newest first (headers only).

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

Input Schema

NameRequiredDescriptionDefault
limitNo
folderNoINBOX
unread_onlyNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 safety is covered. The description adds genuine behavior beyond them: results are sorted newest-first and contain headers only, not message bodies, which tells the agent what it will and won't get back. It does not mention the default page size or any pagination behavior.

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 the resource first, then ordering and return scope. Every clause carries information and there is no filler.

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?

An output schema exists, so return values need not be explained, and the description still flags the headers-only payload and newest-first ordering. The main gap is that the three undocumented parameters, especially unread_only, get no explanation, which matters for an agent choosing arguments.

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

Parameters2/5

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

Schema description coverage is 0% across three parameters, so the description must carry the load. It only weakly implies the folder parameter ('of a folder') and says nothing about limit or unread_only, leaving two of three parameters with no meaning beyond bare titles and defaults.

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 ... emails of a folder') plus ordering ('newest first') and content scope ('headers only'). It implicitly contrasts with search_emails but never names it, so sibling differentiation stops short of explicit.

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?

The phrase 'most recent emails of a folder' implies a browse-recent workflow, and 'headers only' hints that read_email is needed for full content, but neither the when-to-use condition nor an alternative tool is stated. Guidance is inferred rather than given.

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