Skip to main content
Glama
feuerdev
by feuerdev

archive_note

Archive or unarchive a Google Keep note by providing its ID and setting the archived status.

Instructions

Archive or unarchive a note.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
note_idYes
archivedNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool handler for 'archive_note'. Gets the note by ID, ensures it is modifiable, sets the archived flag, syncs with Google Keep, and returns the serialized note as JSON.
    @mcp.tool()
    def archive_note(note_id: str, archived: bool = True) -> str:
        """Archive or unarchive a note."""
        keep, note = _get_note_or_raise(note_id)
        _ensure_modifiable(note)
    
        note.archived = archived
        keep.sync()
        return json.dumps(serialize_note(note))
  • The @mcp.tool() decorator registers 'archive_note' as an MCP tool with FastMCP.
    @mcp.tool()
    def archive_note(note_id: str, archived: bool = True) -> str:
  • Helper function used by archive_note to retrieve the note by ID, raising an error if not found.
    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 used by archive_note to ensure the note can be modified before archiving.
    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?

No annotations are provided, so the description must convey behavioral traits. It only states the toggle behavior without explaining what archiving entails (e.g., visibility, searchability, or side effects). The threshold for transparency is not met.

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 a single concise sentence, which is efficient. However, it could be structured to include brief parameter hints without becoming verbose. The front-loading is adequate.

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 2 parameters, no annotations, an output schema, and sibling tools with similar actions (trash_note, restore_note), the description is incomplete. It does not clarify how archiving differs from trashing or deleting, leaving significant gaps for the agent.

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?

Schema description coverage is 0%, yet the description adds no meaning to the parameters. It does not explain that `note_id` identifies the note or that `archived` toggles the state with a default of true. The agent gains no additional insight beyond the raw schema.

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 (archive or unarchive) and the resource (a note). The tool's name aligns with this, and it distinguishes from sibling tools like trash_note or delete_note by implying a reversible state change.

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 use this tool versus alternatives such as trash_note, delete_note, or restore_note. The description lacks context for decision-making, leaving the agent to infer usage without explicit instructions.

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