Skip to main content
Glama
feuerdev
by feuerdev

update_note

Update the title or text of an existing note by providing its ID. Modify note properties without replacing the entire note.

Instructions

Update a note's properties.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
note_idYes
titleNo
textNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The actual update_note tool handler function. Uses @mcp.tool() decorator. Retrieves the note via _get_note_or_raise, validates it with _ensure_modifiable, updates title/text if provided, syncs via keep, and returns serialized note JSON.
    @mcp.tool()
    def update_note(note_id: str, title: str | None = None, text: str | None = None) -> str:
        """Update a note's properties."""
        keep, note = _get_note_or_raise(note_id)
        _ensure_modifiable(note)
    
        if title is not None:
            note.title = title
        if text is not None:
            note.text = text
    
        keep.sync()
        return json.dumps(serialize_note(note))
  • The @mcp.tool() decorator on line 174 registers update_note as an MCP tool with FastMCP instance created here.
    mcp = FastMCP("keep")
  • _get_note_or_raise helper: retrieves the Keep client and note by ID, raises 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
  • _ensure_modifiable helper: checks if the note can be modified (has keep-mcp label or UNSAFE_MODE enabled), raises ValueError if not.
    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)"
            )
  • serialize_note helper: converts a Keep note object to a dictionary for JSON response.
    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?

The description only indicates mutation (update) but offers no details on side effects, idempotency, permissions, or whether it overwrites or merges. With no annotations, the description's minimal disclosure is insufficient.

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 extremely concise (one sentence, 4 words), but it sacrifices necessary detail. It could be more informative without being verbose.

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?

Despite a simple tool and output schema, the description omits parameter usage, behavioral traits, and usage context. It is not complete enough for agents to invoke confidently.

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%, and the description does not explain any parameters. It fails to add meaning beyond the raw schema, leaving agents without guidance on required note_id or optional title/text.

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?

The description 'Update a note's properties' clearly states the verb (update) and resource (note), but does not specify which properties, relying on the schema. It distinguishes from siblings like create or delete.

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 create_note, archive_note, or set_note_color. The description provides no context for decision-making.

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