Apple Reminders MCP Server

Overview Schema Source Related Servers Discussions Admin

update_reminder

Modify existing Apple Reminders by changing title, notes, due date, priority, tags, list, or flagged status to keep tasks current and organized.

Instructions

Update an existing reminder with new attributes

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": {
      "id": "<id>",
      "title": "<title>"
    },
    "name": "update_reminder"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	The reminder ID to update (required)
`title`	Yes	New title for the reminder (required)
`notes`	No	New notes for the reminder
`listName`	No	Move to a different list
`dueDate`	No	New due date in ISO 8601 format
`priority`	No	Priority: 0=none, 1=high/urgent (!!!), 5=medium, 9=low
`tags`	No	New tags
`flagged`	No	Whether to flag this reminder
`url`	No	URL to associate

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 9, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries full burden but only states it updates attributes without disclosing behavioral traits. It lacks details on permissions required, whether updates are reversible, rate limits, error handling, or what happens to unspecified attributes (e.g., partial vs. full updates).

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?

The description is a single, efficient sentence that front-loads the core action ('update an existing reminder') without unnecessary words. Every part earns its place, making it highly concise and well-structured.

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?

Given the complexity of a mutation tool with 9 parameters, no annotations, and no output schema, the description is incomplete. It fails to address key contextual aspects like behavioral transparency, usage guidelines, or output expectations, leaving significant gaps for an AI agent.

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 fully documents all 9 parameters. The description adds no additional meaning beyond implying 'new attributes' map to the parameters, but doesn't clarify semantics like how tags replace or merge, or format specifics beyond the schema. Baseline 3 is appropriate as the schema does the heavy lifting.

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?

The description clearly states the verb ('update') and resource ('existing reminder'), specifying it modifies attributes. It distinguishes from create_reminder by focusing on existing items, though it doesn't explicitly differentiate from other sibling tools like complete_reminder or uncomplete_reminder.

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 tool versus alternatives is provided. The description doesn't mention prerequisites (e.g., needing an existing reminder ID), exclusions, or comparisons to sibling tools like complete_reminder or delete_reminder, leaving usage context unclear.

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

Deploy Server