Skip to main content
Glama
emguide

Headless Obsidian MCP

by emguide

search_notes

Search notes in an Obsidian vault using ripgrep with optional filters for folder, tags, or frontmatter conditions. Supports pagination and context lines.

Instructions

Search notes with ripgrep, optionally scoped by folder, tags, or a frontmatter where filter (index-resolved candidates, then rg over just those notes). Paginates over matching files: returns { results, truncated, files_returned, files_skipped, files_omitted, matches_capped_in }. Each match carries line_number (file-absolute, ripgrep's) and body_line (1-based body-relative with frontmatter stripped — the same line convention as get_outline/list_tasks/set_task_state, so a hit can be handed straight to those tools; null for hits inside the frontmatter block or in a file the index does not track).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoRestrict to notes carrying these tags (leading '#' optional).
limitNoMax number of files (result entries) to return (default: 20, 0 = unlimited)
matchNoSemantics of tags: 'any' (default) or 'all'.
whereNoRestrict to notes whose frontmatter satisfies these conditions (query_notes syntax).
folderNoRestrict to notes under this folder.
offsetNoMatching files to skip, for pagination (default 0).
patternYesThe search pattern to use with ripgrep
multilineNoEnable multiline matching
whole_wordNoMatch whole words only
context_linesNoNumber of context lines to show (default: 5)
case_sensitiveNoCase sensitive search (default: false)
max_matches_per_fileNoMax matches to return per file (default: 20, 0 = unlimited)
Behavior4/5

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

Discloses pagination behavior with returned fields, explains line_number and body_line conventions, and notes special cases (null for frontmatter hits or untracked files). No annotations provided, so description carries burden well.

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?

Single paragraph with front-loaded core action. Dense but efficient; no unnecessary words. Could be slightly more structured for readability.

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?

Given 12 parameters, no output schema, and no annotations, description covers pagination output, match fields, and nuance of body_line. Lacks details on performance bounds or error conditions, but sufficient for selection.

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?

Schema coverage is 100%, so baseline is 3. Description adds context on return structure and index-resolved approach, but does not significantly enhance parameter meanings beyond 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?

Clearly states 'Search notes with ripgrep' and describes scoping by folder, tags, or frontmatter filters. Distinguishes from sibling search_notes_ranked by not mentioning ranking, but does not explicitly differentiate.

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 on when to use this tool versus alternatives like search_notes_ranked or query_notes. Does not mention when-not-to-use or prerequisites.

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/emguide/headless-obsidian-mcp'

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