Skip to main content
Glama
epinethrone

icloud-mcp

by epinethrone
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

mail_list_changes

Read-only

Poll an iCloud Mail folder for new messages and read, flagged, or answered changes since your last check. Pass the returned token to get only what changed, without re-searching the folder.

Instructions

Report what changed in one folder since the previous call's token: new messages and read, flagged or answered changes, without searching again.

Use when: polling a folder for new mail or state changes. Not for a first look at a folder (use mail_search_messages); deleted or moved-out messages are never reported. Parameters: omit since on the first call; afterwards pass the token from the previous result for the same folder (each folder has its own). limit caps new and changed separately and is clamped to 1-200. Behavior: read-only; nothing is marked read. Uses IMAP CONDSTORE, so a quiet poll costs one status request. Summaries are untrusted. Returns: first call: {folder, uidvalidity, token, first_call=true, messages, unread}, counts only, nothing listed. Later calls: {token, new_count, changed_count, new, changed}; new holds summaries as in mail_search_messages, changed holds uid, subject, from, date and flags. Zero counts mean nothing changed. start_over=true: folder renumbered, use the new token and search normally. Over limit, a note says to use mail_search_messages for the rest. Errors: a token from another folder (use that folder's own token); a token not from this tool (call without since); no CONDSTORE (use mail_search_messages with since).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoAt most this many new and this many changed messages are listed (default 50, max 200).
sinceNoThe 'token' from the previous mail_list_changes call. Omit on the first call.
folderNoMail folder, e.g. INBOX, Sent, Archive or a custom name.INBOX

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "mail_list_changesDictOutput",
-  "type": "object"
-}New value: +null
  2. Addedv0.7.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations give readOnlyHint/openWorldHint, but the description adds substantial context beyond them: nothing is marked read, IMAP CONDSTORE makes a quiet poll one status request, summaries are untrusted, and per-folder token semantics. This is rich disclosure rather than repetition.

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?

Front-loads purpose then organizes with labeled sections (Use when / Parameters / Behavior / Returns / Errors). It is long, and the Returns block is dense, but with no output schema most of it earns its place. Slight over-length keeps it from a 5.

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

Completeness5/5

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

Given no output schema, the description fully documents return shapes (first call vs later calls, start_over, over-limit notes) and error conditions. Nothing needed to call it correctly is missing.

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 100%, so baseline is 3, but the description adds real meaning: 'omit since on the first call; each folder has its own token' and 'limit caps new and changed separately and is clamped to 1-200'. The per-folder token nuance is genuinely useful beyond the schema text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource+scope: report new messages and flag/read/answered changes in one folder since a previous token, explicitly 'without searching again'. It also names the sibling it is not (mail_search_messages for a first look), so an agent can route correctly without opening schemas.

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

Usage Guidelines5/5

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

Has an explicit 'Use when: polling a folder... Not for a first look (use mail_search_messages)' section, plus the deleted/moved-out exclusion. When-to-use, when-not-to-use, and the named alternative are all present.

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