Skip to main content
Glama
docdyhr
by docdyhr

search_notes

Read-onlyIdempotent

Search Simplenote notes with boolean operators, date filters, tags, fuzzy matching, pagination, and sorting to precisely retrieve the notes you need.

Instructions

Search for notes in Simplenote with advanced capabilities including fuzzy matching, pagination, and sorting support. To find the most recently updated note on a topic, use sort_by='modifydate' with sort_direction='desc' and limit=1. Use list_tags first if you need to discover available tags before filtering.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoTags to filter by — all must be present (array of strings; a comma-separated string is also accepted). Use 'untagged' to find notes without tags.
fuzzyNoEnable fuzzy matching to handle typos and approximate matches (default: false)
limitNoMaximum number of results to return per page (default: 20)
queryYesThe search query (supports boolean operators AND, OR, NOT; phrase matching with quotes; tag filters like tag:work; date filters like from:2023-01-01 to:2023-12-31 or natural language dates like from:last_week to:yesterday)
offsetNoNumber of results to skip for pagination (default: 0)
pinnedNoFilter by pin status: true = only pinned notes, false = only unpinned notes, omit = all notes
sort_byNoSort results by field. Default: 'relevance' (by match quality). Use 'modifydate' to get the most recently updated notes first. Use 'createdate' to get the newest-created notes first.
to_dateNoFilter notes modified before this date (ISO format e.g. 2023-12-31, or natural language e.g. today, yesterday)
from_dateNoFilter notes modified after this date (ISO format e.g. 2023-01-01, or natural language e.g. yesterday, last_week, 3_days_ago)
created_afterNoFilter notes created after this date (ISO format e.g. 2023-01-01)
modified_afterNoFilter notes modified after this date (ISO format e.g. 2023-06-01)
sort_directionNoSort direction: 'desc' (newest/highest first, default) or 'asc' (oldest/lowest first).
Behavior5/5

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

Annotations already indicate readOnly and idempotent. The description adds valuable behavioral context: supports fuzzy matching, boolean operators, phrase matching, natural language dates, and sorted results. 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.

Conciseness5/5

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

Three concise sentences: first sentence states purpose, second gives a practical tip, third suggests a complementary tool. No redundant information, and the main purpose is front-loaded.

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

Completeness4/5

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

With 12 parameters, 100% schema coverage, and no output schema, the description covers search behavior, filtering, sorting, and pagination. It could mention the return format (likely a list of note summaries) but overall is sufficiently complete for an optimized tool description.

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 coverage is 100%, so baseline is 3. The description adds extra meaning by providing usage context (e.g., natural language dates, sort_by examples) and cross-referencing list_tags. However, most parameters are already well-documented in 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 states 'Search for notes in Simplenote with advanced capabilities including...' which clearly identifies the tool's action (search) and resource (notes). It distinguishes from siblings like list_notes (full listing) and find_untagged_notes by specifying advanced search features.

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

Usage Guidelines5/5

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

Provides explicit usage examples: 'To find the most recently updated note on a topic, use sort_by='modifydate'...' and advises using list_tags for tag discovery. This guides the agent on when and how to use the tool effectively.

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/docdyhr/simplenote-mcp-server'

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