Skip to main content
Glama
adamzaidi

icloud-mcp

by adamzaidi

bulk_flag

Flag or unflag multiple emails at once using filters like sender, date, subject, or size to organize your iCloud Mail efficiently.

Instructions

Flag or unflag emails matching any combination of filters in bulk

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
flaggedYesTrue for flagged only, false for unflagged only
mailboxNoMailbox (default INBOX)
senderNoMatch exact sender email address
domainNoMatch any sender from this domain (e.g. substack.com)
subjectNoKeyword to match in subject
beforeNoOnly emails before this date (YYYY-MM-DD)
sinceNoOnly emails since this date (YYYY-MM-DD)
unreadNoTrue for unread only, false for read only
largerNoOnly emails larger than this size in KB
smallerNoOnly emails smaller than this size in KB
hasAttachmentNoOnly emails with attachments (client-side BODYSTRUCTURE scan — must be combined with other filters that narrow results to under 500 emails first)
accountNoAccount name to use (e.g. 'icloud', 'gmail'). Defaults to first configured account. Use list_accounts to see available accounts.
Behavior2/5

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

No annotations are provided, so the description must carry full behavioral disclosure. While 'Flag or unflag' indicates mutation, the description fails to mention operational limits (like the 500-email limit for attachment scanning noted only in the schema), error handling, or performance characteristics of bulk operations.

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?

The description is a single, efficient sentence front-loaded with the action verbs. However, extreme brevity (9 words) contributes to underspecification for a complex 12-parameter tool; additional context on scope or safety would justify a longer description.

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

Completeness2/5

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

For a complex bulk mutation tool with 12 filtering parameters, no annotations, and no output schema, the 9-word description is inadequate. It lacks safety warnings about mass-modifying email states, return value documentation, or guidance on the 'hasAttachment' limitation.

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

Parameters3/5

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

With 100% schema description coverage across 12 parameters, the schema carries the semantic load. The description adds minimal parameter context beyond acknowledging 'filters' generally. It does not clarify the relationship between the required 'flagged' parameter and the 'Flag or unflag' action described.

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?

The description uses specific verbs ('Flag or unflag') and identifies the resource ('emails'). It distinguishes from singular 'flag_email' by specifying 'in bulk' and implies differentiation from 'bulk_flag_by_sender' by emphasizing 'any combination of filters'. However, it could explicitly clarify when to use this versus the sender-specific variant.

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?

The description provides no guidance on when to use this tool versus alternatives like 'flag_email' (single) or 'bulk_flag_by_sender'. It omits prerequisites, safety warnings for bulk operations, or whether this operation is reversible.

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/adamzaidi/icloud-mcp'

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