Skip to main content
Glama

update_reminder

Update specific fields of an existing Apple Reminder—rename, change due date/time, move to another list, set priority, modify notes or tags, or clear the due date. Only fields you specify are modified; others remain unchanged.

Instructions

Update fields on an existing reminder. Only provided fields are changed. If you update notes OR tags individually, the other is preserved automatically.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesCurrent name of the reminder to find.
tagsNoReplace tags (notes preserved if not provided).
notesNoReplace notes text (tags preserved if not provided).
due_dateNoNew due date in YYYY-MM-DD format.
due_timeNoNew due time in HH:MM 24-hour format.
new_nameNoRename the reminder to this.
priorityNoNew priority.
list_nameNoCurrent list to narrow the search.
new_list_nameNoMove reminder to this list.
clear_due_dateNoSet to true to remove the due date entirely.
Behavior3/5

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

No annotations provided, so description carries the burden. It discloses partial update and notes/tags preservation, but omits error handling, idempotency, or requirement for the reminder to exist.

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 sentences, front-loaded with the main action, then key behavioral detail. No superfluous 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?

With 10 parameters and no output schema or annotations, the description covers core behavior but lacks details on response format, error conditions, and parameter interactions like clear_due_date.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds value by clarifying partial update behavior and tag/notes interaction, which goes beyond schema parameter 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?

The description states 'Update fields on an existing reminder' with a specific verb and resource. It clearly distinguishes from sibling tools like create_reminder and delete_reminder.

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

Usage Guidelines4/5

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

The description explains partial update behavior ('Only provided fields are changed'), guiding correct usage. It does not explicitly exclude alternatives but the context of sibling tools makes usage clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kamrenkennedy/apple-reminders-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server