Skip to main content
Glama
Sign In
icloud-mcp

icloud-mcp

by adamzaidi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

delete_older_than

Remove emails older than a specified number of days from an iCloud Mail mailbox. Use dry run to preview changes before deleting.

Instructions

Delete all emails older than a certain number of days

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": {
      "days": "<days>"
    },
    "name": "delete_older_than"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysYesDelete emails older than this many days
dryRunNoIf true, report exactly what would change and do not modify anything
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

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure, yet it says nothing about permanence, reversibility, or required permissions. It mentions 'Delete all' but never notes that this is a destructive, likely irreversible mass operation, and it does not surface the schema's dryRun safeguard, which matters a lot for a bulk delete.

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?

A single efficient sentence that front-loads the verb and the subject. It earns its place but is arguably under-specified for a destructive bulk operation, which is a completeness issue rather than a conciseness one.

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 mass-destruction tool with no annotations and no output schema, the description is too thin. It omits the dryRun preview option, the mailbox scoping, and any warning about permanence—context an agent needs to invoke this safely.

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 days, dryRun, and mailbox are each already documented in the schema (including the dryRun safety semantics). The description adds no syntax or format detail beyond restating the day-threshold concept, so the baseline of 3 is appropriate.

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?

States a specific verb ('Delete') with a precise resource and scope ('all emails older than a certain number of days' by a day threshold). This distinguishes it from generic deletes like delete_email or bulk_delete. However, it does not differentiate itself from the near-identical sibling archive_older_than, which shares the exact 'older than N days' pattern, leaving the agent to infer the destructive-vs-archive distinction.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives such as archive_older_than or empty_trash. The description gives no indication of when this threshold-based bulk deletion is appropriate versus other delete tools in the sibling set.

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