Skip to main content
Glama
chandshy
by chandshy

Bulk Mark Emails Read/Unread

bulk_mark_read
Idempotent

Mark multiple emails as read or unread with progress notifications and success/failed counts. Specify the source folder to ensure correct operation.

Instructions

Mark multiple emails as read or unread. Emits progress notifications. Returns success/failed counts. Pass sourceFolder whenever the UIDs came from a folder other than INBOX.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
isReadNo
emailIdsYesArray of email UIDs
account_idNoOptional account ID to route this call to (multi-account configs). Omit to use the active account. Configured account IDs are listed in the settings UI (Accounts tab).
sourceFolderNoFolder the UID(s) live in (e.g. INBOX, Folders/Work, Labels/Foo). Strongly recommended whenever the UIDs came from a folder other than INBOX — IMAP UIDs are folder-scoped, so without this the wrong folder may be selected and the operation may silently no-op. Avoid passing 'All Mail' as the source: it is a union view of every folder, not a real location, so moves out of it can silently do nothing — pass the message's actual folder instead. Moving to the folder a message is already in is a no-op.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorsYes
failedYes
successYes
Behavior5/5

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

The description adds significant behavioral context beyond annotations: it mentions progress notifications, return counts, and warns about IMAP UID scoping and the risk of silent no-ops with 'All Mail'. The idempotentHint and destructiveHint are also consistent.

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?

The description is two sentences, each adding essential information. It is front-loaded with the core action and quickly covers critical usage advice without unnecessary detail.

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?

The description covers the action, return format, progress notifications, and a key caveat about sourceFolder. Given the output schema likely documents return structure, it is reasonably complete, though it could mention error handling or when to prefer this over single mark_read.

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 description adds meaning to the sourceFolder parameter by explaining the folder-scoping issue and warning against 'All Mail'. It also notes the default isRead value. With 75% schema coverage, the description provides valuable extra guidance.

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?

The description clearly states the tool marks multiple emails as read or unread, distinguishing it from single-email alternatives like mark_email_read. It also mentions progress notifications and return counts.

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

Usage Guidelines4/5

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

The description advises passing sourceFolder when UIDs are from a non-INBOX folder, which is critical for correct operation. However, it does not explicitly compare to other bulk tools like bulk_star or bulk_move.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/chandshy/mailpouch'

If you have feedback or need assistance with the MCP directory API, please join our Discord server