Skip to main content
Glama
Sign In
icloud-mcp

icloud-mcp

by adamzaidi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

bulk_delete_by_subject

Delete all emails matching a subject pattern. Bulk remove messages by subject keyword from a specified mailbox, with an optional dry run to preview changes.

Instructions

Delete all emails matching a subject pattern

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": {
      "subject": "<subject>"
    },
    "name": "bulk_delete_by_subject"
  }
}

Input Schema

NameRequiredDescriptionDefault
dryRunNoIf true, report exactly what would change and do not modify anything
mailboxNoMailbox (default INBOX)
subjectYesSubject keyword to match

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

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose that deletion is destructive and likely irreversible, whether messages go to trash, whether the dryRun parameter is honored, or what permissions or scope limits apply. The phrase 'all emails matching' gives only minimal scope context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence with no wasted words. However, its brevity comes at the cost of omitting important operational details, making it under-specified rather than optimally concise for a destructive bulk operation.

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?

Given that this is a destructive bulk-delete tool with no annotations, no output schema, and no mention of dryRun or irreversibility, the description is not complete enough for safe invocation. It leaves the agent without critical context about side effects, reversibility, and the safety mechanism available in the schema.

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 all three parameters including the dryRun safety behavior. The description adds only 'subject pattern' versus the schema's 'Subject keyword to match', which is marginal added meaning. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states a specific verb ('Delete') and resource ('emails') plus a scoping condition ('matching a subject pattern'), which distinguishes it from sender-based siblings like bulk_delete_by_sender. However, it does not explicitly name those siblings or clarify how it differs from generic bulk_delete, so sibling differentiation is implied rather than explicit.

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 gives no guidance on when to use this tool versus alternatives such as bulk_delete_by_sender, bulk_delete, or delete_email. It also omits any prerequisites, warnings, or conditions for safe use, leaving the agent to infer usage from the name alone.

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