Skip to main content
Glama
feuerdev
by feuerdev

delete_list_item

Remove a specific item from a Google Keep checklist using its note and item IDs.

Instructions

Delete a checklist item.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
note_idYes
item_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The tool handler implementation for delete_list_item. Registered via @mcp.tool() decorator. Gets the note, validates it's modifiable and is a list type, finds the item by ID, calls item.delete(), syncs with Keep API, and returns a JSON message.
    @mcp.tool()
    def delete_list_item(note_id: str, item_id: str) -> str:
        """Delete a checklist item."""
        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")
    
        item.delete()
        keep.sync()
        return json.dumps({"message": f"List item {item_id} marked for deletion"})
  • The @mcp.tool() decorator registers delete_list_item as an MCP tool on the FastMCP server instance.
    @mcp.tool()
  • Input schema: accepts note_id (str) and item_id (str). Returns a JSON string with a message field.
    def delete_list_item(note_id: str, item_id: str) -> str:
  • Helper function used by delete_list_item to fetch the note by ID or raise ValueError.
    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 used by delete_list_item to ensure the note can be modified before deleting an item.
    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)"
            )
Behavior2/5

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

The description only says 'Delete', implying mutation, but fails to disclose any behavioral traits such as whether the operation is irreversible, what happens to associated data, or authorization requirements. With no annotations, this 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 very concise (one sentence), which is efficient, but it sacrifices necessary detail. It is not overly verbose, but borderline under-specified.

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 having an output schema (not shown), the description does not mention return values or error conditions. For a delete operation with sibling tools, more context about what the tool requires and returns is needed.

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?

The input schema has 0% description coverage and the description does not explain what note_id or item_id represent. The parameter names hint at their roles, but no additional meaning is provided beyond the schema.

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 action (Delete) and the resource (a checklist item). It is not a tautology and provides the basic purpose, though it lacks specificity to distinguish from sibling tools like add_list_item or update_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 provided on when to use this tool versus alternatives like add_list_item or update_list_item. There are no prerequisites or context about needed permissions or valid states.

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