Skip to main content
Glama
feuerdev
by feuerdev

add_list_item

Add a new item to a checklist note in Google Keep. Specify the note ID, item text, and optionally mark it as checked.

Instructions

Add an item to a checklist note.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
note_idYes
textYes
checkedNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'add_list_item' tool. Decorated with @mcp.tool(), it retrieves a note by ID, verifies it's modifiable and is a List type, adds an item with the given text and checked state, syncs with Google Keep, and returns the note_id and item_id as JSON.
    @mcp.tool()
    def add_list_item(note_id: str, text: str, checked: bool = False) -> str:
        """Add an item to a checklist note."""
        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.add(text=text, checked=checked)
        keep.sync()
        return json.dumps({"note_id": note.id, "item_id": item.id})
  • Registration of the tool using the @mcp.tool() decorator on the add_list_item function, which registers it with the FastMCP server instance.
    @mcp.tool()
  • Helper function _get_note_or_raise used by the handler to look up a note by ID and raise 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 _ensure_modifiable used by the handler to verify a note can be modified (has keep-mcp label or UNSAFE_MODE is enabled).
    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)"
            )

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description must carry the behavioral disclosure burden. It states a mutation occurs, but does not explain append behavior, whether checked defaults to false, failure modes, permissions, or reversibility.

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 clear, front-loaded sentence with no filler. It is appropriately concise, though it sacrifices useful detail.

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?

For a mutation tool with no annotations and zero schema descriptions, the description is incomplete. It omits prerequisites such as the note being a checklist, behavior when the note does not exist, and the role of the checked parameter. The output schema covers return values, so that is not the gap.

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%, so the description needs to compensate. It provides only a slight relational hint that an item is added to a checklist note, but it does not explain the meaning of note_id, text, or checked beyond their names.

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 uses a specific verb and resource: 'Add an item to a checklist note.' It clearly identifies the operation and distinguishes it from sibling tools like update_list_item and delete_list_item.

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 given about when to use this tool versus alternatives such as update_list_item, delete_list_item, or create_list. There are no preconditions, exclusions, or context cues to help the agent choose this tool correctly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.