keep_delete_note
Apaga uma nota permanentemente (não dá pra desfazer).
Bulk support: accepts note_ids for batched execution.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| unsafe | No | ||
| account | No | ||
| note_id | Yes | ||
| note_ids | No |
Google Keep
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4.1/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description explicitly states the deletion is permanent and irreversible, which is critical behavioral information. It also discloses bulk execution, so it is transparent about the tool's effects.
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 concise and to the point, leading with the main action and adding bulk support in a second sentence without unnecessary detail.
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?
While the core purpose and bulk behavior are covered, the lack of explanation for the unsafe and account parameters leaves the description incomplete for fully informed usage.
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 description clarifies the note_ids parameter for batch operations, but does not explain the unsafe or account parameters, leaving their semantics unclear.
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 tool permanently deletes a note, distinguishing it from trash or soft-delete operations. It also mentions bulk support, which further clarifies its purpose.
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?
It mentions bulk support but does not explicitly contrast with alternative tools like trash or update, leaving the specific use-case context somewhat open.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
B3.2/5.0
Disambiguation4/5
The keep_* tools are clearly distinct with verb_noun patterns, and the platform tools (authenticate, connect, marketplace, etc.) serve separate functions. No two tools appear to do the same thing, though the mix of Keep and platform tools could cause an agent to briefly confuse context.
Naming Consistency3/5
The keep_* tools follow a consistent keep_verb_noun pattern, but the platform tools use simple unrelated names (authenticate, connect, marketplace) without the prefix, breaking consistency across the set.
Tool Count2/5
At 30 tools, the server exceeds the recommended range. While the Keep operations are comprehensive, the inclusion of 6 platform management tools inflates the count and makes the surface heavier than necessary for a Keep-focused server.
Completeness4/5
The Keep tools cover full lifecycle: create/read/update/delete for notes, list items, labels, and collaborators, plus archive/trash/pin and media retrieval. The platform tools add connection and marketplace capabilities. Minor gaps like bulk operations on notes are partially addressed with bulk support fields.