Skip to main content
Glama
feuerdev
by feuerdev

update_list_item

Update the text or checked status of an existing checklist item in a Google Keep note by specifying the note and item IDs.

Instructions

Update checklist item text and/or checked state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
note_idYes
item_idYes
textNo
checkedNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the update_list_item MCP tool. Updates a checklist item's text and/or checked state, validates the note is a list, and returns the serialized note.
    @mcp.tool()
    def update_list_item(note_id: str, item_id: str, text: str | None = None, checked: bool | None = None) -> str:
        """Update checklist item text and/or checked state."""
        keep, note = _get_note_or_raise(note_id)
        _ensure_modifiable(note)
    
        if not isinstance(note, gkeepapi.node.List):
            raise ValueError(f"Note with ID {note_id} is not a list")
    
        item = note.get(item_id)
        if not item:
            raise ValueError(f"List item with ID {item_id} not found")
    
        if text is not None:
            item.text = text
        if checked is not None:
            item.checked = checked
    
        keep.sync()
        return json.dumps(serialize_note(note))
  • The @mcp.tool() decorator registers the function as an MCP tool named 'update_list_item'.
    @mcp.tool()
  • Helper used by the handler to retrieve the note and raise 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 used by the handler to ensure the note can be modified.
    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)"
            )
  • Helper function that serializes a note (including its list items) to a dict, used by the handler to produce the return value.
    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?

Without annotations, the description carries full burden. It states 'update' implying mutation, but fails to disclose side effects, idempotency, permissions, or behavior on missing items. The agent has minimal insight into the tool's operational impact.

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 extraneous words. It is front-loaded with the action and resource, and every word earns its place. Ideal conciseness.

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 4 parameters, zero schema descriptions, no annotations, and an output schema, the description omits return values, error handling, and usage context (e.g., authentication). It is insufficient for a complete understanding of the tool's behavior in a complex workflow.

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

Parameters3/5

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

With 0% schema description coverage, the description adds meaning by naming the two optional parameters that can be updated. However, it does not explain the note_id and item_id identifiers, assuming the agent understands their format or origin. The description provides marginal value over the schema titles.

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 verb 'update' and the resource 'checklist item', specifying the modifiable attributes 'text and/or checked state'. It effectively distinguishes from sibling tools like add_list_item and delete_list_item by implying modification of existing items.

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. It does not mention prerequisites (e.g., item must exist), potential error conditions, or situations where this tool is preferable. The brevity leaves the agent without context for appropriate invocation.

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