Skip to main content
Glama
feuerdev
by feuerdev

update_note

Modify Google Keep notes by updating their title or text content via the Keep MCP server. Requires the note ID and supports optional fields for title and text changes.

Instructions

Update a note's properties.

Args:
    note_id (str): The ID of the note to update
    title (str, optional): New title for the note
    text (str, optional): New text content for the note
    
Returns:
    str: JSON string containing the updated note's data
    
Raises:
    ValueError: If the note doesn't exist or cannot be modified

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
note_idYes
textNo
titleNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The @mcp.tool() decorator registers the update_note tool with the FastMCP server.
    @mcp.tool()
  • The handler function for the 'update_note' tool. Retrieves the note by ID using the Google Keep client, performs modification checks, updates title and/or text as provided, syncs changes, and returns serialized JSON of the updated note.
    def update_note(note_id: str, title: str = None, text: str = None) -> str:
        """
        Update a note's properties.
        
        Args:
            note_id (str): The ID of the note to update
            title (str, optional): New title for the note
            text (str, optional): New text content for the note
            
        Returns:
            str: JSON string containing the updated note's data
            
        Raises:
            ValueError: If the note doesn't exist or cannot be modified
        """
        keep = get_client()
        note = keep.get(note_id)
        
        if not note:
            raise ValueError(f"Note with ID {note_id} not found")
        
        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)")
        
        if title is not None:
            note.title = title
        if text is not None:
            note.text = text
        
        keep.sync()  # Ensure changes are saved to the server
        return json.dumps(serialize_note(note))
  • The function signature and docstring define the input schema (parameters: note_id required str, title/text optional str) and output (str JSON), which is used by FastMCP for tool schema.
    def update_note(note_id: str, title: str = None, text: str = None) -> str:
        """
        Update a note's properties.
        
        Args:
            note_id (str): The ID of the note to update
            title (str, optional): New title for the note
            text (str, optional): New text content for the note
            
        Returns:
            str: JSON string containing the updated note's data
            
        Raises:
            ValueError: If the note doesn't exist or cannot be modified
        """
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses that the tool modifies note properties and raises errors for non-existent or unmodifiable notes, which is useful behavioral context. However, it lacks details on permissions, side effects, or rate limits, leaving gaps for a mutation tool.

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 well-structured with clear sections (Args, Returns, Raises), uses bullet-like formatting for parameters, and is front-loaded with the core purpose. Every sentence adds value without redundancy, making it highly efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (mutation with 3 parameters), no annotations, and an output schema present (which handles return values), the description is fairly complete. It covers purpose, parameters, returns, and errors, though it could benefit from more behavioral context like permissions or side effects.

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

Parameters4/5

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

The description adds significant value beyond the input schema, which has 0% description coverage. It explains that 'note_id' identifies the note to update, 'title' is a new optional title, and 'text' is new optional content, clarifying the purpose of each parameter effectively.

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 clearly states the verb 'Update' and resource 'note's properties', making the purpose understandable. However, it doesn't differentiate from sibling tools like 'create_note' or 'delete_note' beyond the obvious update vs create/delete distinction, which is why it doesn't reach a 5.

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?

The description provides no guidance on when to use this tool versus alternatives like 'create_note' or 'delete_note'. It mentions errors for non-existent notes, but offers no explicit usage context, prerequisites, or comparisons to siblings.

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

Related 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