Skip to main content
Glama
feuerdev
by feuerdev

restore_note

Restore a deleted or trashed note by providing its unique note ID.

Instructions

Restore a trashed/deleted note.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
note_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The actual handler function for the 'restore_note' tool. It retrieves the note, ensures it's modifiable, calls untrash() and undelete() on the note, syncs with Google Keep, and returns the serialized note as JSON.
    @mcp.tool()
    def restore_note(note_id: str) -> str:
        """Restore a trashed/deleted note."""
        keep, note = _get_note_or_raise(note_id)
        _ensure_modifiable(note)
    
        note.untrash()
        note.undelete()
        keep.sync()
        return json.dumps(serialize_note(note))
  • The tool is registered with the MCP server using the @mcp.tool() decorator on the restore_note function. The FastMCP instance is created at line 14.
    @mcp.tool()
  • The function signature defines the input schema: restore_note takes a single string parameter 'note_id' and returns a string (JSON).
    def restore_note(note_id: str) -> str:
  • Helper function _get_note_or_raise: retrieves a note by ID from the Keep client, raising ValueError 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 serialize_note: serializes a Google Keep note object into a dictionary including id, title, text, trashed status, color, labels, and media.
    def serialize_note(note):
        """
        Serialize a Google Keep note into a dictionary.
        
        Args:
            note: A Google Keep note object
            
        Returns:
            dict: A dictionary containing the note's id, title, text, pinned status, color and labels
        """
        payload = {
            'id': note.id,
            'title': note.title,
            'text': note.text,
            'type': note.type.value,
            'pinned': note.pinned,
            'archived': note.archived,
            'trashed': note.trashed,
            'color': note.color.value if note.color else None,
            'labels': [serialize_label(label) for label in note.labels.all()],
            'collaborators': list(note.collaborators.all()),
        }
    
        if hasattr(note, 'items'):
            payload['items'] = [serialize_list_item(item) for item in note.items]
    
        payload['media'] = [
            {
                'blob_id': blob.id,
                'type': blob.blob.type.value if blob.blob and blob.blob.type else None,
            }
            for blob in note.blobs
        ]
    
        return payload
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states the basic function without mentioning side effects, permissions, or state transitions (e.g., what happens if note is not trashed).

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 a single sentence with no redundant words, achieving maximum conciseness for a straightforward tool.

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?

While the tool is simple (one parameter, one action), the description lacks output details (despite an output schema existing) and fails to convey any edge cases or behavioral nuance, making it minimally complete.

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?

Schema description coverage is 0%, yet the description does not elaborate on the 'note_id' parameter beyond its type, missing context like expected format or source of the ID.

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 ('Restore') and the resource ('a trashed/deleted note'), using a specific verb-noun pair that distinguishes from siblings like 'trash_note' and 'delete_note'.

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, no mention of prerequisites (e.g., note must be in trash), and no explicit when-not-to-use conditions.

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