Skip to main content
Glama
feuerdev
by feuerdev

delete_note

Delete a note from Google Keep by providing its note ID. The note is marked for deletion and removed.

Instructions

Delete a note (mark for deletion).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
note_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The tool handler that executes the delete_note logic: looks up the note by ID, ensures it's modifiable, marks it for deletion, syncs, and returns a JSON confirmation message.
    @mcp.tool()
    def delete_note(note_id: str) -> str:
        """Delete a note (mark for deletion)."""
        keep, note = _get_note_or_raise(note_id)
        _ensure_modifiable(note)
    
        note.delete()
        keep.sync()
        return json.dumps({"message": f"Note {note_id} marked for deletion"})
  • The @mcp.tool() decorator registers delete_note as an MCP tool with the FastMCP server.
    @mcp.tool()
    def delete_note(note_id: str) -> str:
  • Helper function that retrieves a note by ID and raises ValueError if not found. Used by delete_note.
    def _get_note_or_raise(note_id: str):
        keep = get_client()
        note = keep.get(note_id)
        if not note:
            raise ValueError(f"Note with ID {note_id} not found")
        return keep, note
  • Helper function that checks if a note can be modified via can_modify_note. Used by delete_note.
    def _ensure_modifiable(note):
        if not can_modify_note(note):
            raise ValueError(
                f"Note with ID {note.id} cannot be modified "
                "(missing keep-mcp label and UNSAFE_MODE is not enabled)"
            )
Behavior2/5

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

Annotations are absent, so the description must disclose behavior. It mentions 'mark for deletion' but does not clarify if deletion is reversible, what permissions are needed, 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.

Conciseness3/5

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

The description is a single short sentence with no fluff, but it is too sparse to be considered well-structured. It sacrifices necessary detail for brevity.

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 presence of multiple related sibling tools, the description is incomplete. It does not explain how this tool differs from 'trash_note' or 'archive_note', nor does it mention any output or error conditions.

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

Parameters1/5

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

The input schema has one parameter (note_id) with 0% coverage. The description adds no additional meaning or constraints beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the verb 'Delete' and resource 'note', but adds 'mark for deletion' which hints at soft delete. However, it does not distinguish from siblings like 'trash_note' or 'archive_note', causing potential confusion.

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 is provided on when to use this tool versus alternatives (e.g., trash_note, archive_note, restore_note). The description lacks context for appropriate use.

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/feuerdev/keep-mcp'

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