keep-mcp

keep_create_list

Create a new Google Keep checklist when the list doesn't already exist. Use this to start a fresh shopping list, then add items separately.

Instructions

Create a new Keep checklist. Use this only if the shopping list does not already exist — prefer keep_add_items on the existing list.

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": "keep_create_list"
  }
}

Input Schema

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

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses the prerequisite that the list should not exist, but it does not state what happens if the list already exists, whether duplicate titles cause errors, or what side effects creation has. For a mutating tool, this leaves important behavioral unknowns.

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?

Two short sentences with no filler. The primary action is front-loaded, and the usage constraint with alternative is stated immediately after. Every word earns its place.

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?

The tool is simple, has an output schema, and the description includes key routing guidance. However, it lacks behavior for duplicate titles and fails to mention the optional items parameter. As a mutation tool with no annotations, these gaps prevent full self-contained understanding.

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?

Schema description coverage is 0%, so the description must compensate, but it says nothing about the 'title' or 'items' parameters. The title is somewhat self-evident from the tool name, but the optional items parameter is completely unexplained—an agent is left to guess whether items can be seeded during creation and how they should be formatted.

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: 'Create a new Keep checklist.' It clearly differentiates this tool from the sibling keep_add_items by stating its distinct role of creating a new list rather than adding to an existing one.

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

Usage Guidelines5/5

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

Explicitly states when to use this tool ('only if the shopping list does not already exist') and names the alternative to prefer in the opposite case ('prefer keep_add_items on the existing list'). This is direct, actionable guidance.

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

Deploy Server