Skip to main content
Glama
epinethrone

icloud-mcp

by epinethrone
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

contacts_delete_group

Destructive

Delete one iCloud contact group by uid and name when asked to remove a group; only the grouping is removed and every member's contact card stays.

Instructions

Delete one contact group by uid; only the grouping goes, every member's contact card stays in the address book.

Use when: the owner explicitly asks to remove a group. Not for removing some people from a group (use contacts_update_group with remove_members), for renaming (use contacts_update_group), or for deleting a person (use contacts_delete_contact). Parameters:

  • uid is the opaque group uid string from contacts_list_groups; copy it exactly (matched case-sensitively). A person's uid gives "No group with uid".

  • name must be that group's name as contacts_list_groups shows it; case and accents are ignored, other differences are not.

  • Both are required and must agree: name is the check that the uid is the group the owner meant. A mismatch deletes nothing and the error names the uid's real group. Behavior: removes the group card from every synced device; it cannot be undone through this connector (recreate it with contacts_create_group if needed). No contact is edited or deleted. The delete is conditional on the version last read, so a group changed elsewhere since is not deleted. Not available when the server runs READ_ONLY. Returns: {deleted: true, uid, name, note}. Errors: a name mismatch is refused with "That uid is the group 'X', not 'Y'. Nothing was deleted."; "No group with uid" (wrong uid or already deleted; a repeat call gives this); "This contact changed since it was read": list the groups again and retry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uidYesGroup uid from contacts_list_groups.
nameYesThe group's exact name, as a check.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "contacts_delete_groupDictOutput",
-  "type": "object"
-}New value: +null
  2. Addedv0.11.0

TDQS

A5/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and non-idempotency, but the description adds substantial context beyond them: irreversibility through the connector, optimistic concurrency ('conditional on the version last read'), unavailability under READ_ONLY, synced-device propagation, and repeat-call behavior. This is a genuinely rich behavioral account for a mutation tool.

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 the effect, then organizes the rest under Use when / Parameters / Behavior / Returns headers. Despite the length, each sentence carries operational content (error strings, concurrency, retry guidance) with no filler or repetition.

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?

With no output schema, the description supplies the return shape ({deleted, uid, name, note}) and the exact error strings an agent must interpret, plus the recovery step for the version conflict. Nothing needed to invoke or recover from this tool is missing.

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 baseline is 3, but the description adds real meaning: uid is matched case-sensitively and must be copied exactly, and name is a fuzzy-but-bounded check (case and accents ignored, other differences not) whose mismatch deletes nothing and reports the uid's real group. That is more than the schema conveys.

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+resource (delete a contact group by uid) and immediately scopes the effect ('only the grouping goes, every member's contact card stays'). This distinguishes it cleanly from contacts_delete_contact and contacts_update_group without opening any schema.

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?

Gives an explicit positive trigger ('the owner explicitly asks to remove a group') and three named exclusions with the correct alternative for each (remove_members via contacts_update_group, renaming via contacts_update_group, deleting a person via contacts_delete_contact). Nothing is left to inference.

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