Skip to main content
Glama
Sign In
icloud-mcp

icloud-mcp

by adamzaidi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

read_inbox

Fetch emails from an iCloud inbox with pagination. Filter by account, mailbox, and unread status to manage multiple accounts.

Instructions

Read emails from an inbox with pagination. Supports multiple accounts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "read_inbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default 1)
limitNoNumber of emails per page (default 10)
accountNoAccount name to read from (e.g. "work", "personal", "school", "icloud"). Omit for default iCloud account.
mailboxNoMailbox to read (default INBOX)
onlyUnreadNoOnly fetch unread emails

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.8.0
    • addedInput schema / properties / account
      Added value: +{
+  "description": "Account name to read from (e.g. \"work\", \"personal\", \"school\", \"icloud\"). Omit for default iCloud account.",
+  "type": "string"
+}
  2. First observedv2.5.1

TDQS

B3.1/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 burden. It discloses pagination and multi-account support, but does not say whether reading marks messages as read, how results are ordered, or what permissions or side effects apply — all important for an inbox read operation.

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?

Two short sentences, front-loaded with the main action and no wasted words.

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

Completeness3/5

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

All five optional parameters are fully described in the schema, and there is no output schema to explain. However, the description does not help the agent choose this tool over the many alternative mail-reading siblings, leaving a meaningful navigation gap.

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 fully documents page, limit, account, mailbox, and onlyUnread. The description only echoes the pagination and account concepts at a high level, adding no syntax, defaults, or edge-case details beyond the schema.

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 ('Read') and resource ('emails from an inbox') plus two capabilities (pagination, multiple accounts). It does not distinguish the tool from close siblings such as search_emails, get_emails_by_date_range, or get_email, so an agent still has to infer when this is the right read operation.

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 guidance on when to use this instead of search_emails, get_emails_by_date_range, get_inbox_summary, or get_email. 'Supports multiple accounts' is a capability statement, not a usage rule or exclusion.

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