Google Keep MCP

delete_label

Permanently remove a specified label from Google Keep by providing its label ID. Use this when a label is no longer needed; requires UNSAFE_MODE=true because deletion is globally destructive.

Instructions

Delete a label. Requires UNSAFE_MODE=true as this is globally destructive.

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": {
      "label_id": "<label_id>"
    },
    "name": "delete_label"
  }
}

Input Schema

Name	Required	Description	Default
`label_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 30, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the transparency burden. It usefully warns that the operation is globally destructive and requires unsafe mode, but it does not clarify whether deletion is irreversible or what happens to notes that use the label, leaving some behavioral ambiguity.

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 two tight sentences with no filler: the action is front-loaded and the critical safety caveat follows immediately. 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?

For a simple one-parameter tool with an output schema, this is mostly adequate, but it omits important context for a destructive operation: the full scope of destruction, irreversibility, or side effects on associated notes. A short additional sentence would make it complete.

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?

The single parameter label_id is self-explanatory from its name and schema title, but the description adds no parameter-level guidance. Since schema description coverage is 0%, the description should compensate, and it does not address how to obtain the ID or any format expectations.

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 ('Delete') and a clear resource ('a label'). It is unambiguous and distinguishes this tool from siblings such as remove_label_from_note or delete_note.

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 provides an explicit prerequisite: UNSAFE_MODE=true, and explains why ('globally destructive'). This gives clear context about when the tool may be invoked, though it does not explicitly name alternatives such as remove_label_from_note.

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