Skip to main content
Glama

Delete Reminder

delete_reminder
DestructiveIdempotent

Delete any reminder by providing its unique ID. Removes the specified reminder from your reminders list.

Instructions

Delete a reminder by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesReminder ID

Implementation Reference

  • The handler for the delete_reminder tool. Registers the tool with McpServer, defines input schema (id), and executes the deletion via runAutomation (Swift: 'delete-reminder' command or JXA fallback using deleteReminderScript). Returns a DeleteResult with {deleted: boolean, name: string}.
    server.registerTool(
      "delete_reminder",
      {
        title: "Delete Reminder",
        description: "Delete a reminder by ID. This action is permanent.",
        inputSchema: {
          id: z.string().max(500).describe("Reminder ID"),
        },
        annotations: {
          readOnlyHint: false,
          destructiveHint: true,
          idempotentHint: true,
          openWorldHint: false,
        },
      },
      async ({ id }) => {
        try {
          const result = await runAutomation<DeleteResult>({
            swift: { command: "delete-reminder", input: { id } },
            jxa: () => deleteReminderScript(id),
          });
          return ok(result);
        } catch (e) {
          return errJxaFor("delete reminder", e);
        }
      },
    );
  • The JXA (JavaScript for Automation) script that actually deletes a reminder using the Apple Reminders app. Finds the reminder by ID, captures its name, calls Reminders.delete(r), and returns a JSON with {deleted: true, name: name}.
    export function deleteReminderScript(id: string): string {
      return `
        const Reminders = Application('Reminders');
        const r = Reminders.reminders.byId('${esc(id)}');
        const name = r.name();
        Reminders.delete(r);
        JSON.stringify({deleted: true, name: name});
      `;
    }
  • The DeleteResult type definition used as the return type for delete_reminder. Contains {deleted: boolean, name: string}.
    export interface DeleteResult {
      deleted: boolean;
      name: string;
    }
  • The export function registerReminderTools(server, config) that registers all reminder tools including delete_reminder on the McpServer.
    export function registerReminderTools(server: McpServer, _config: AirMcpConfig): void {
Behavior3/5

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

Annotations already indicate destructive and idempotent behavior. The description adds no extra behavioral context beyond 'delete', so it is adequate but not enhanced.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise (one sentence) and front-loaded, but lacks any supplementary details that might be helpful without being verbose.

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?

For a simple delete operation with clear annotations and a single parameter, the description is sufficient. No output schema is present, but this is acceptable for a void-returning delete.

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?

The single parameter 'id' is described in the schema as 'Reminder ID' with no additional explanation in the tool description. Schema coverage is 100%, so baseline score applies.

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 clearly states the action (delete) and the resource (reminder by ID), which is specific and distinct from sibling tools like complete_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 delete versus other reminder actions (e.g., complete, update). No prerequisites or context for using this tool.

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/heznpc/AirMCP'

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