Skip to main content
Glama

Find Doc by Title

find_doc_by_title
Read-onlyIdempotent

Find all documents matching an exact title in an AFFiNE workspace. Supports case-sensitive or case-insensitive matching and returns metadata for each match.

Instructions

Resolve docs by exact title. Returns ALL matches up to limit (callers handle ambiguity). Case-sensitive by default; pass caseInsensitive: true to fold case. Reads workspace metadata — fast, no per-doc fetch. Unlike search_docs (which is always case-insensitive and capped at limit 20), this tool defaults to case-sensitive matching and returns up to limit matches (default 50, max 200). Prefer this over search_docs when you know the exact title and want every match. Returns: { query, caseInsensitive, matches: [{ id, title, createdAt, updatedAt, inTrash }], workspaceDocCount, truncated }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax matches to return (default: 50).
titleYesThe exact title to match.
workspaceIdNoWorkspace ID (optional if AFFINE_WORKSPACE_ID is set).
caseInsensitiveNoIf true, fold case for comparison (default: false).
Behavior5/5

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

Discloses that it reads workspace metadata without per-doc fetch, and describes return structure including truncated flag. Annotations (readOnlyHint, idempotentHint) are consistent, and no contradictions.

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?

Well-structured and front-loaded, but slightly verbose. Every sentence adds value, but could be tightened without losing clarity.

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 no output schema, the description provides a detailed return structure, behavior (fast, no per-doc fetch), and explains the difference from sibling. Highly complete for a read 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%, and the description adds some context (e.g., default limit of 50, max 200) but does not significantly enhance understanding beyond what the parameter descriptions provide.

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 resolves docs by exact title, providing a specific verb and resource. It distinguishes itself from the sibling 'search_docs' by noting case-sensitivity and higher limit.

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?

Explicitly advises preferring this tool over 'search_docs' when exact title is known and all matches are desired. Also notes case-sensitivity default and optional switch.

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/DAWNCR0W/affine-mcp-server'

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