Skip to main content
Glama
Sign In
icloud-mcp

icloud-mcp

by adamzaidi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

bulk_flag_by_sender

Flag or unflag all emails from one sender in an iCloud Mail mailbox; use dryRun to preview changes first.

Instructions

Flag or unflag all emails from a specific sender

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": {
      "sender": "<sender>",
      "flagged": "<flagged>"
    },
    "name": "bulk_flag_by_sender"
  }
}

Input Schema

NameRequiredDescriptionDefault
dryRunNoIf true, report exactly what would change and do not modify anything
senderYesSender email address
flaggedYesTrue to flag, false to unflag
mailboxNoMailbox (default INBOX)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.8.0
    • addedInput schema / properties / dryRun
      Added value: +{
+  "description": "If true, report exactly what would change and do not modify anything",
+  "type": "boolean"
+}
  2. First observedv2.5.1

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden yet only restates the mutation. It does not disclose that flagging is reversible, whether it spans mailboxes, permission/auth requirements, or the existence of the dryRun safety path (which is left to the schema alone). Thin for a bulk mutation tool.

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?

A single front-loaded sentence with zero redundancy. The core scope ('all emails from a specific sender') is stated up front with no filler.

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 bulk mutation with no annotations and no output schema, the description should convey more about impact, reversibility, or scope (e.g., which mailbox, what a run returns). The schema covers the parameters, but the behavioral context an agent needs to call this safely is missing.

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?

Schema description coverage is 100%, so the schema already documents sender, flagged, mailbox, and dryRun. The description adds no format, default, or edge-case detail beyond what the schema provides; baseline 3 applies.

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 uses a specific verb pair (flag/unflag) plus a precise scope ('all emails from a specific sender'), clearly distinguishing it from single-target flag_email and generic bulk_flag. An agent can identify the operation and its bulk-by-sender semantics without opening the schema.

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

Usage Guidelines3/5

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

Usage is implied by the bulk 'by sender' scoping, but there is no explicit when-to-use, when-not-to-use, or named alternative (e.g., bulk_flag for specific IDs vs this for whole-sender sweeps). Nothing tells the agent which of the many bulk_* siblings to prefer.

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