Skip to main content
Glama
suckerfish
by suckerfish

search_notes

Find specific Google Keep notes and lists by text, labels, color, dates, or other attributes. Supports regex search, sorting, and filtering by status.

Instructions

Search Google Keep notes and lists.

Args: query: Text to search in title and body (supports regex). labels: Filter by label names. color: Filter by color name (e.g. "yellow", "blue"). pinned: Filter by pinned status. archived: Filter by archived status. trashed: Include trashed notes. created_after: ISO 8601 date/datetime; only notes created at or after this. created_before: ISO 8601 date/datetime; only notes created at or before this. updated_after: ISO 8601 date/datetime; only notes updated at or after this. updated_before: ISO 8601 date/datetime; only notes updated at or before this. sort_by: Sort by "created", "updated", "edited", or "title". Unsorted (arbitrary internal order) if omitted. sort_desc: Sort descending (newest/Z-first) when sort_by is set. Default True. offset: Number of results to skip (for paging through large result sets). limit: Maximum number of results to return.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
colorNo
limitNo
queryNo
labelsNo
offsetNo
pinnedNo
sort_byNo
trashedNo
archivedNo
sort_descNo
created_afterNo
updated_afterNo
created_beforeNo
updated_beforeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so description bears full burden. It discloses search behavior, filter options, sorting, and pagination. However, it does not explicitly state it is read-only or mention rate limits, though these are implied.

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 well-structured with a clear purpose sentence followed by parameter list. It is somewhat verbose but efficient with no wasted sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 14 parameters and an output schema available, the description covers all input details comprehensively. It is complete for an agent to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully explains each parameter (query regex, color names, ISO 8601 dates, sort options, etc.), adding significant value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool searches Google Keep notes and lists. It is specific but does not explicitly differentiate from sibling tools like get_note or list functions, though the name distinguishes it.

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?

No explicit guidance on when to use this tool versus alternatives. The description implies usage for search/filtering but lacks exclusions or references to sibling tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/suckerfish/google_keep_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server