Google Keep MCP

create_list

Create a new checklist note in Google Keep, with items unchecked by default and the keep-mcp safety label automatically applied.

Instructions

Create a new checklist note. Auto-applies the 'keep-mcp' safety label. Items are provided as a list of strings (all unchecked by default).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>"
    },
    "name": "create_list"
  }
}

Input Schema

Name	Required	Description	Default
`items`	No
`title`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 30, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carried the burden and it discloses two non-obvious behaviors: the automatic 'keep-mcp' safety label and the default unchecked state of items. It does not go into permission requirements or what happens if items is null, but the provided side-effect information is meaningful.

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?

Three short sentences, each earning its place: the action, the autoatic label side effect, and the item format/default state. The most important purpose information is front-loaded in the first sentence.

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?

For a two-parameter create tool with an output schema, the description covers the core purpose, a key hidden side effect, and the main parameter semantics. It is slightly incomplete only in not routing between checklist and regular note creation, but nothing required to invoke it correctly is missing.

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?

Schema description coverage is 0%, so the description must compensate; it explains that items are a list of strings and start unchecked, which adds real meaning beyond the schema. It does not describe the required title parameter, leaving that property solely to the schema.

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 opens with 'Create a new checklist note,' which names a specific verb and resource, and the checklist qualifier separates it from the regular create_note sibling. The auto-applied 'keep-mcp' safety label adds another distinct behavioral marker.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'Create a new checklist note' implies the tool is for checklist creation, but it never names alternatives such as create_note for regular notes or add_list_item for later additions. There is a clear implied use case but no explicit when-to-use or when-not-to-use guidance.

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