Skip to main content
Glama
Sign In
google-keep-mcp

google-keep-mcp

by suckerfish
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

remove_label_from_note

Removes a specified label from a Google Keep note by providing the note ID and label name.

Instructions

Remove a label from a note.

Args: note_id: The ID of the note. label_name: The label name to remove.

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": {
      "note_id": "<note_id>",
      "label_name": "<label_name>"
    },
    "name": "remove_label_from_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
note_idYes
label_nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits like idempotency, permissions, or error conditions. It only states the action without addressing what happens if the label does not exist on the note or if the operation is reversible.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded with the main action. The Args block is somewhat redundant but does not overly bloat the text.

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?

For a mutation tool with two parameters and an output schema, the description lacks details on return values, error handling, or behavior in edge cases (e.g., non-existent label).

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?

The input schema has 0% description coverage, so the description adds minimal meaning by restating parameter names with 'The ID of the note' and 'The label name to remove'. This is basic but does not provide format or constraints.

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 clearly states the verb 'Remove' and the resource 'label from a note'. It distinguishes from sibling 'add_label_to_note' which does the opposite, and from 'delete_label' which deletes the label entirely.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as 'delete_label' or 'add_label_to_note'. The description does not specify context or prerequisites.

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

Deploy Server

Other Tools