keep-mcp

keep_remove_items

Delete specified items from a Google Keep checklist by name. Provide item names, and optionally identify the note or list to target.

Instructions

Delete items from a Keep checklist by name.

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": {
      "items": "<items>"
    },
    "name": "keep_remove_items"
  }
}

Input Schema

Name	Required	Description	Default
`items`	Yes
`note_id`	No
`list_title`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the destructive action ('delete') but does not disclose permanence, whether the operation is reversible, what happens if an item is not found, or how the target checklist is selected. For a deleting tool, this is a significant transparency gap.

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?

The description is a single, front-loaded sentence with no filler. Every word contributes to identifying the action, target, and selection method.

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?

The tool has three parameters, no annotations, and no schema-level descriptions, yet the description does not explain how to specify the checklist or what the deletion semantics are. The output schema mitigates return-value concerns, but the description is still too sparse for an agent to invoke the tool correctly in all realistic cases.

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 must compensate for parameter meaning. The phrase 'by name' gives some semantics to the items parameter, but note_id and list_title are left unexplained. It is unclear whether one or both are required, which is which, or how they interact.

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 states a specific verb and resource: 'Delete items from a Keep checklist by name.' It is clearly distinct from siblings like keep_add_items, keep_check_items, and keep_uncheck_items, which involve adding or toggling rather than removing.

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 description implies the use case: remove checklist items by name. However, it does not explicitly explain when to prefer this over alternatives, nor does it describe prerequisites such as specifying a note_id or list_title to locate the correct checklist. Usage guidance is mostly left to inference from the tool name and siblings.

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

Deploy Server