Skip to main content
Glama
feuerdev
by feuerdev

create_list

Create a checklist note in Google Keep with optional title and items. Each item includes a task and its checked status.

Instructions

Create a new checklist note.

items should be objects like: {"text": "task", "checked": false}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNo
itemsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool handler for create_list: creates a new checklist note with optional items, adds the keep-mcp label, syncs, and returns serialized JSON.
    @mcp.tool()
    def create_list(title: str | None = None, items: list[dict[str, Any]] | None = None) -> str:
        """
        Create a new checklist note.
    
        items should be objects like: {"text": "task", "checked": false}
        """
        keep = get_client()
        formatted_items = None
        if items:
            formatted_items = [
                (item.get("text", ""), bool(item.get("checked", False))) for item in items
            ]
    
        note = keep.createList(title=title, items=formatted_items)
    
        label = keep.findLabel("keep-mcp")
        if not label:
            label = keep.createLabel("keep-mcp")
        note.labels.add(label)
    
        keep.sync()
        return json.dumps(serialize_note(note))
  • Registration of create_list as an MCP tool via the @mcp.tool() decorator on line 95.
    @mcp.tool()
    def create_list(title: str | None = None, items: list[dict[str, Any]] | None = None) -> str:
  • Type signature and docstring defining the input schema: optional title (str) and items (list of dicts with text/checked fields), returns JSON string.
    def create_list(title: str | None = None, items: list[dict[str, Any]] | None = None) -> str:
        """
        Create a new checklist note.
    
        items should be objects like: {"text": "task", "checked": false}
  • Helper function serialize_list_item used to convert checklist items into dictionaries for the JSON response.
    def serialize_list_item(item):
        return {
            'id': item.id,
            'text': item.text,
            'checked': item.checked,
            'parent_item_id': item.parent_item.id if item.parent_item else None,
        }
  • Helper function serialize_note used to serialize the created list note into a JSON-serializable dictionary, including items via serialize_list_item.
    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?

No annotations provided, so description must convey behavioral traits. Only states 'create' and gives item format, omitting details like side effects, permissions, or return behavior.

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?

Two concise sentences with front-loaded purpose. The example adds value without excessive verbosity.

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

Completeness3/5

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

Tool has 2 parameters with no schema descriptions and no annotations. Description partially covers items but not title or output behavior. Output schema exists, so return values are covered, but overall completeness is moderate.

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?

Schema has 0% description coverage, but description adds meaningful structure for 'items' parameter with example {'text': 'task', 'checked': false}. This compensates for absent schema descriptions, though 'title' is not elaborated.

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?

Description clearly states 'Create a new checklist note.', specifying the action (create) and resource (checklist note). It distinguishes from siblings like 'create_note' (plain note) and 'add_list_item' (modifies existing list).

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 explicit guidance on when to use this tool versus alternatives like 'create_note' or 'add_list_item'. The description implies it's for new checklists but lacks context on exclusions or prerequisites.

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