Skip to main content
Glama
epinethrone

icloud-mcp

by epinethrone
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

contacts_create_group

Create a new contact group in iCloud Contacts, optionally adding initial members, for inviting or emailing a set of people together.

Instructions

Create a new contact group in the owner's address book (it shows in the Contacts app), optionally with its first members.

Use when: the owner wants a new named group, for example to invite or mail a set of people together. Not for changing an existing group's name or members (use contacts_update_group), for finding existing groups (use contacts_list_groups), or for creating a person (use contacts_create_contact). Parameters:

  • name: 1-100 characters; runs of spaces are collapsed.

  • members: person uids from contacts_search_contacts; omitted means an empty group; duplicates are dropped. Behavior:

  • Writes one group card to the first (default) address book and syncs it to the owner's devices; no contact card is changed.

  • A name that already exists (ignoring case and accents) is refused, so a repeat never makes a second group.

  • Every member uid is checked first; if one is unknown nothing is created.

  • Not available when the server runs READ_ONLY. Returns: {created: true, uid, name, members (count)}. Errors:

  • "There is already a group called ...": use contacts_list_groups to get its uid.

  • "Not contacts in this address book: ..." names the bad uids.

  • a name outside 1-100 characters is refused.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the new group.
membersNoContact uids (from contacts_search_contacts).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "contacts_create_groupDictOutput",
-  "type": "object"
-}New value: +null
  2. Changed1 schema field changedv0.12.0
    • changedInput schema / properties / members / description
      Previous value: -"Contact uids (from contacts_search)."New value: +"Contact uids (from contacts_search_contacts)."
  3. Addedv0.11.0

TDQS

A5/5.0
Behavior5/5

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

Adds substantial behavior beyond annotations: writes one group card to the default address book and syncs to devices, never changes contact cards, refuses duplicate names ignoring case and accents, validates all member uids before creating anything, and is unavailable in READ_ONLY mode. Annotations already cover safety hints, and the description enriches rather than contradicts them.

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?

Front-loads purpose and usage, then uses labeled sections for parameters, behavior, returns, and errors. Despite its length, every section provides actionable information for a write tool with no output schema.

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

Completeness5/5

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

Covers the full lifecycle an agent needs: prerequisites, side effects, validation rules, failure modes, and the return shape. With no output schema, the description appropriately supplies return and error details itself.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaningful constraints: name is 1-100 characters with space-run collapsing, members are uids from contacts_search_contacts, omitting members creates an empty group, and duplicates are dropped. This goes well beyond the schema's simple property descriptions.

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?

States a specific verb and resource: 'Create a new contact group in the owner's address book.' It distinguishes itself from siblings by explicitly naming contacts_update_group, contacts_list_groups, and contacts_create_contact as alternatives for other needs.

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

Usage Guidelines5/5

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

Provides an explicit 'Use when' condition and a 'Not for' clause listing three sibling tools with the specific scenarios each handles. An agent can route correctly without opening another schema.

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