Skip to main content
Glama
iCloud MCP Server Apple

iCloud MCP Server Apple

List Chats

list-chats
Read-onlyIdempotent

Retrieve recent iMessage and SMS conversations, newest first, and filter by date to find chats active within a specific period.

Instructions

List recent iMessage/SMS conversations, most recent first. Use since to get only the conversations active after a date (e.g. the last 7 days).

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": "list-chats"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of conversations to return (default 20)
sinceNoOnly conversations with a message at or after this date (ISO 8601, optional)

Output Schema

NameRequiredDescriptionDefault
itemsYesRecent conversations
totalYesNumber of items returned

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.2.2
    • changedInput schema / properties / limit / description
      Previous value: -"Number of conversations to show (default 20)"New value: +"Maximum number of conversations to return (default 20)"
    • changedInput schema / properties / limit / maximum
      Previous value: -200New value: +1000
    • addedInput schema / properties / since
      Added value: +{
      +  "description": "Only conversations with a message at or after this date (ISO 8601, optional)",
      +  "type": "string"
      +}
  2. Addedv2.1.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent and closed-world, so the safety profile is covered. The description adds the sort order, which is genuinely useful behavior not in the annotations, but says nothing about pagination, truncation, or what a listed conversation contains.

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 with the core purpose and sort order front-loaded, followed by the only non-obvious parameter note. No filler or repetition of schema content.

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

Completeness4/5

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

With an output schema present and full annotation and parameter coverage, the description only needs to convey purpose and ordering, which it does. It falls short of 5 only because nothing tells the agent how a listed conversation relates to read-messages.

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 coverage is 100%, so both `limit` and `since` are already documented with bounds and defaults, giving a baseline of 3. The "e.g. the last 7 days" example adds a small amount of practical framing but no syntax or semantics 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 and resource ("List recent iMessage/SMS conversations") plus an ordering guarantee ("most recent first"), which separates it from read-messages, a message-level reader. It never names that sibling explicitly, so the differentiation is implicit rather than stated.

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?

The second sentence gives guidance on using `since` for a time-bounded listing, which implies browsing/discovery usage. There is no explicit when-not-to-use or pointer to read-messages for drilling into a single conversation's contents, which is the main routing decision an agent faces here.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.