Skip to main content
Glama

roam_search_for_tag

Search for blocks containing a specific tag in Roam Research. Optionally filter by page, near tag, or case sensitivity. Supports pagination. Use to retrieve tagged memories or organize content.

Instructions

Search for blocks containing a specific tag. Use primary_tag for the tag to find, and optionally page_title_uid to limit search to a specific page. Supports pagination via limit and offset. Use this tool to search for memories tagged with the ROAM_MEMORIES_TAG.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
primary_tagYesThe main tag to search for (without the [[ ]] brackets)
page_title_uidNoOptional: Title or UID of the page to search in (UID is preferred for accuracy). Defaults to today's daily page if not provided.
near_tagNoOptional: Another tag to filter results by - will only return blocks where both tags appear
case_sensitiveNoOptional: Whether the search should be case-sensitive. If false, it will search for the provided tag, capitalized versions, and first word capitalized versions.
limitNoOptional: The maximum number of results to return. Defaults to 50. Use -1 for no limit, but be aware that very large results sets can impact performance.
offsetNoOptional: The number of results to skip before returning matches. Useful for pagination. Defaults to 0.
graphNoTarget graph key from ROAM_GRAPHS config. Defaults to ROAM_DEFAULT_GRAPH. Only needed in multi-graph mode.
write_keyNoWrite confirmation key. Required for write operations on non-default graphs when write_key is configured.
Behavior3/5

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

No annotations provided. The description explains pagination, defaults, and case_sensitive behavior but lacks details on performance impact (beyond limit=-1 note) or any side 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?

Three sentences, each providing distinct information: purpose, parameter usage, and specific use case. No wasted words.

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 8 parameters, no output schema, and no annotations, the description covers core functionality and parameter usage. It lacks info on return format or error handling but is sufficient for a search tool.

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. The description reinforces the schema but doesn't add significant new information beyond what is already in parameter descriptions.

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 it searches for blocks containing a specific tag, and mentions a specific use case (ROAM_MEMORIES_TAG). This distinguishes it from sibling tools like roam_search_by_text or roam_search_block_refs.

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?

The description explains how to use primary_tag and optional page_title_uid, and mentions pagination. It does not explicitly contrast with other search tools, but provides enough guidance for typical usage.

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/2b3pro/roam-research-mcp'

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