Skip to main content
Glama

delete_note

Destructive

Delete a note by ID, moving it to the Recently Deleted folder for 30 days so it can be recovered.

Instructions

Delete a note. Notes moves it to the Recently Deleted folder, where it stays for 30 days.

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>"
    },
    "name": "delete_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesNote id from search_notes (it starts with x-coredata://).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds genuinely new behavior: deletion is a soft delete into Recently Deleted with a 30-day retention window. That materially changes how an agent should weigh the operation. It does not mention restore mechanics, permissions, or whether the 30 days can be shortened, keeping it below 5.

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?

Two short sentences with the destructive action front-loaded and the retention detail immediately after. Minor grammar slip ("Notes moves it") slightly hurts polish but costs no comprehension.

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?

For a single-parameter delete with full annotation coverage and no output schema, the description supplies everything needed to call it correctly and to understand the consequence: soft delete with a 30-day recovery window. No meaningful gap remains for a tool of this complexity.

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%, and the single id parameter is already documented with its x-coredata:// format and provenance from search_notes. The description adds no further meaning about the parameter, so the baseline of 3 applies.

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?

States a specific verb (delete) and resource (note) in the first two words, which unambiguously separates it from sibling delete_* tools targeting calendars, contacts, events, folders, and messages. It does not explicitly contrast with move_note, which is the closest conceptual alternative, so it falls short of a 5.

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?

The description gives no when-to-use or when-not-to-use guidance and names no alternative (e.g., move_note for relocating a note without deletion). The intended action is inferable from the name and verb, but the agent receives no routing guidance beyond that.

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