# Triage, label, archive and clean up an inbox

> Triage, label, archive and clean up an inbox: 4 companies fully do it, 6 with a limit, 32 carry the tag. Every listing in Mailbox access with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/mailbox-access.triage-and-file/
- Markdown: https://www.anchorterminal.com/niches/mailbox-access.triage-and-file/index.md (~1,300 tokens)
- Slim: https://www.anchorterminal.com/niches/mailbox-access.triage-and-file/index.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/mailbox-access.triage-and-file/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Four or more companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 4 | 6 | 32 | 11 | 4 |

## What counts as done

Every message matching the rule carries the label or sits in the named folder, nothing outside the rule is moved or deleted, and the run reports counts per action.

How agents ask for it: clean up my inbox; label everything from the bank; archive newsletters older than a month; what's high priority today

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **EmailEngine (Postal Systems OÜ, Narva mnt 5, 10117 Tallinn, Estonia, registry code 14971894)**: update_messages and move_messages act on every message in one folder matching a search in one call, and the tool guidance runs search_messages first with the same criteria so the agent sees what will change.
- **Fastmail API (JMAP) (Fastmail Pty Ltd, ACN 142 646 580, PO Box 234, Collins Street West, VIC 8007, Australia)**: Email/set patches mailboxIds and keywords on many emails in one call and returns updated and notUpdated per ID, so the agent can report counts and see each failure.
- **Gmail API (Google LLC)**: messages.batchModify adds and removes labels on up to 1,000 message IDs per request, and the IDs come from a messages.list query, so the agent counts precisely what it changed; gmail.labels and gmail.modify scope it.
- **Zoho Mail API (Zoho Corporation Private Limited)**: Move emails takes an array of message IDs, or thread IDs, and a destfolderId in one call, and Apply labels tags messages, so a rule's matches are filed in bulk under UPDATE scopes.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Aurinko Email API (Yoxel, Inc.)**: POST /messages/{id}/status updates one message at a time and folders can be listed and created, but no bulk modify or documented move-to-folder parameter was found, and label search is Gmail-only.
- **email-agent-mcp (UseJunior)**: label_email, mark_read and move_to_folder work on Microsoft 365, one message per call, but on Gmail they return NOT_SUPPORTED before any request, so filing fails there.
- **Himalaya (No legal entity found. Copyright Clément DOUIN (soywod))**: Flags, copy, move and delete take message IDs under --allow-write, but there is no confirmation before move or delete, and acc-12 restored a mailbox from snapshots after an agent damaged it over IMAP.
- **Nylas Email API (Nylas, Inc.)**: PUT on a message or thread updates folders, starred and unread, and folders can be created, but each message or thread is a separate call with no bulk operation, and list calls fan out to many provider calls and hit 429s.
- **Outlook Mail (Microsoft Graph) (Microsoft Corporation)**: POST /messages/{id}/move takes a destinationId per message, but the reference says a move creates a new copy and removes the original, so IDs change unless ImmutableId is requested, and there is no bulk move beyond 20-request JSON batches.
- **Unipile (UNIPILE SAS)**: Update an email moves it by folders or marks it read, but one email per call, Outlook and IMAP take one folder only, and a folder move updates the entire thread when the email is part of a conversation, moving messages outside the rule.

## Couldn't check

The docs were closed to us, or silent. These carry no mark either way.

- **CloudPost (CloudPost (James Brooks))**: No docs or tool schemas; the site claims organising mail with approval, but which moves and labels exist and whether counts come back can't be read.

## What stops agents finishing

- labels, flags and moves unsupported on a provider (email-agent-mcp on Gmail returns NOT_SUPPORTED)
- no confirmation before delete or move
- a community IMAP server that corrupts the mailbox

## Around it

Before: mailbox-access.connect-mailboxes. After: notifications.digest.

## Where this comes from

Weight 11 of 100 in Mailbox access: 4 of 36 counted mentions (acc-02, 03, 08, 12); acc-36 is second-hand and not counted

As data: https://www.anchorterminal.com/api/v1/use-cases/mailbox-access.triage-and-file.json, or the MCP tool get_use_case with id mailbox-access.triage-and-file. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
