Skip to main content
Glama

maily_list_messages

Lists recent messages for a specified email profile, letting you filter by category, limit results, and show only unread mail.

Instructions

Lists the recent messages of a profile.

profile   : email or name of the profile (e.g. 'alex@example.com' or 'Personal').
category  : 'inbox' | 'primary' | 'promotions' | 'social' | 'updates' | 'forums' | 'archived' | 'all'.
limit     : maximum number (default 20).
unread_only : keep unread messages only.

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": {
      "profile": "<profile>"
    },
    "name": "maily_list_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
profileYes
categoryNoinbox
unread_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.1

TDQS

B3.1/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden. 'Lists' implies read-only, but nothing confirms non-destructiveness, states pagination/offset behavior for the limit cap, or explains ordering beyond the word 'recent'.

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?

Purpose sentence first, then a compact per-parameter block with zero filler. The aligned list format is slightly unusual but readable and every line carries information.

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?

For a 4-parameter listing tool with no annotations and no output schema, the description documents inputs adequately but says nothing about the returned message shape or result ordering. An agent knows how to call it but not what to expect back.

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?

Schema coverage is 0% and the description compensates well: it names all four parameters, gives a profile example, enumerates the allowed category values (the schema has no enum), and states defaults for limit and unread_only. Minor gap: no guidance on invalid categories or partial-name matching for profile.

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 ('Lists the recent messages of a profile') with a scope hint ('recent'). It does not distinguish itself from the sibling maily_search, which an agent could equally plausibly pick for retrieving messages.

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 statement of when to use this versus maily_search or maily_get_message, and no prerequisites (e.g., whether a sync via maily_sync must run first). The category enum implies filtering but the description never says to use this for browsing versus searching.

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