Skip to main content
Glama

Find Bear Notes

bear-search-notes
Read-onlyIdempotent

Search across Bear note titles, body, and OCR text to find matching notes. Filter results by tag, date, or pinned status for precise retrieval.

Instructions

Search your Bear notes for words or phrases. The search looks across note titles, body content, and OCR text in attached images and PDFs, returning matching notes ranked by relevance with a snippet of the matching context — so you can see what matched without opening the note. For best results, search with a phrase or several words from what you're looking for; a single word also works. Also supports filtering by tag, by creation/modification date range, or by pinned status — combine these with a search term, or use them on their own to browse without searching. Trashed and archived notes are not included.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoTag to filter notes by (leading # is stripped if present)
termNoWords to search for. Results are ranked by relevance — notes covering more of what you typed rank higher. Pass natural keywords for the typical case (e.g., "quarterly planning notes"). Hyphenated or punctuated identifiers like "bear-notes-mcp" or "2026-04-15" are matched as a phrase when used alone; in multi-word queries they are treated like any other word.
limitNoMaximum number of results to return (default: 30, min: 1)
pinnedNoSet to true to return only pinned notes: if combined with tag, will return pinned notes with that tag, otherwise only globally pinned notes.
createdAfterNoFilter notes created on or after this date. Supports: relative dates ("today", "yesterday", "last week", "start of last month"), ISO format (YYYY-MM-DD). Use "start of last month" for the beginning of the previous month.
createdBeforeNoFilter notes created on or before this date. Supports: relative dates ("today", "yesterday", "last week", "end of last month"), ISO format (YYYY-MM-DD). Use "end of last month" for the end of the previous month.
modifiedAfterNoFilter notes modified on or after this date. Supports: relative dates ("today", "yesterday", "last week", "start of last month"), ISO format (YYYY-MM-DD). Use "start of last month" for the beginning of the previous month.
modifiedBeforeNoFilter notes modified on or before this date. Supports: relative dates ("today", "yesterday", "last week", "end of last month"), ISO format (YYYY-MM-DD). Use "end of last month" for the end of the previous month.
Behavior4/5

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

Annotations indicate read-only, idempotent behavior. Description adds context: notes are ranked by relevance, returns snippets, and excludes trashed/archived notes. No contradictions with annotations.

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?

Structured in a logical flow: purpose, return format, usage tips, then filter details. Front-loaded with the core function. All sentences add value, though slightly verbose for a summary.

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 8 optional parameters and no output schema, the description thoroughly covers search scope, result format, filter options, and exclusions (trashed/archived). Provides sufficient context for an agent to use effectively.

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 covers 100% of parameters with descriptions. The tool description adds extra context: explains term matching with hyphenated identifiers, that tag strips leading #, and relative date formats. That adds value beyond the schema.

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 searches Bear notes for words or phrases, covering titles, body, and OCR content. It distinguishes itself from siblings (e.g., bear-list-tags, bear-open-note) by focusing on search and retrieval.

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?

Provides explicit guidance on best practices (phrase or several words for best results) and explains how to combine filters or use them independently. Notes that trashed/archived notes are excluded, but does not explicitly mention alternatives among siblings.

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/vasylenko/bear-notes-mcp'

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