keep-mcp

keep_get

Retrieve a Google Keep note or checklist via list title or note ID; falls back to default list. Returns item text and checked state.

Instructions

Get one Keep note or checklist. Pass list_title (e.g. 'Shopping') or note_id from keep_find. If both are omitted, uses KEEP_DEFAULT_LIST. Lists include each item's text and checked state.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "keep_get"
  }
}

Input Schema

Name	Required	Description	Default
`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

A4.2/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses the default selection behavior and that lists include each item's text and checked state, but it does not explicitly confirm the operation is read-only, nor does it explain precedence if both list_title and note_id are supplied.

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 compact sentences with no filler. The core action is front-loaded, parameter guidance follows, and the only output detail included is the item text and checked state, which is directly useful.

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 simple getter with two optional parameters and an output schema, the description covers the selection mechanism, the default behavior, and list output structure. The main gaps are the lack of an explicit read-only statement and behavior when both parameters are provided, but these are minor for this tool.

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 description coverage is 0%, so the description must add meaning to the parameters, and it does: list_title is a named label like 'Shopping', and note_id comes from keep_find. It also clarifies the default when both are omitted. It could add what happens if both parameters are provided.

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 ('Get') and resource ('one Keep note or checklist'), and clearly distinguishes itself from keep_find by referencing note_id from keep_find. It is immediately obvious what this tool does and how it differs from the sibling reading tool.

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

Usage Guidelines4/5

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

The description tells the agent exactly how to select a note: by list_title or note_id, with a concrete example, and what happens if both are omitted (KEEP_DEFAULT_LIST). It does not explicitly state when not to use this tool, but the sibling names make the alternative operations clear.

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

Deploy Server