Skip to main content
Glama

Delete Note

notes_delete
Destructive

Delete a note from Apple Notes by stable ID or title, requiring explicit confirmation to prevent accidental removal.

Instructions

Delete a note by stable id or title. Requires confirm=True.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNo
accountNo
confirmNo
note_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

The description adds that confirm=True is required, beyond the destructiveHint annotation. However, it omits details like whether deletion is permanent or any side effects.

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 two sentences, straight to the point, with no unnecessary 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?

For a destructive tool with 4 parameters and an output schema (present but not detailed), the description could address parameter conflicts (e.g., both id and title provided) or error conditions.

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

Parameters2/5

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

With 0% schema coverage, the description should explain parameters. It only hints at 'by stable id or title' for note_id/title but ignores account and confirm (beyond 'requires confirm=True').

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 tool deletes a note, using either a stable ID or title. This distinguishes it from sibling tools like notes_create or notes_search.

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

Usage Guidelines3/5

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

The description mentions require confirm=True, indicating a precondition, but doesn't specify when to use this tool versus other note-related tools or any alternatives for deleting notes.

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/abhinavag-svg/apple-ecosystem-mcp'

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