Tools
tools/list is the authoritative source for what the server currently exposes. At the time of writing there are
thirteen tools:
| Area | Tools |
|---|---|
| Read your library | search_library, get_references_from_library, get_collections_from_library, get_libraries, get_text_content |
| Modify your library | update_references, update_collections, save_to_library, highlight_text |
| Search external catalogs | find_papers, lookup_papers, get_inbound_cites, get_outbound_references |
Library search output
search_library accepts output_format: MARKDOWN (default), MINIMAL, or JSON.
Markdown groups matching passages under reference cards with citation metadata and file IDs.
Minimal emits one line per match with its citekey, page, offsets and excerpt, without file IDs.
JSON returns { query, resultCount, referenceCount, data: [{ reference, matches }], total? };
batched queries retain the { results: [...] } wrapper in input order. Each match preserves its
resultType, highlighted metadata or snippet, and any file, page, character-offset and annotation identifiers.
Reference summaries reuse the SDK's published date and files attachment objects. Markdown cards
share the reference-list renderer: a ### Citekey - Title heading, Markdown website and main-PDF
viewer links, and additional attachments as nested bullets under Files:. A lone main PDF appears
only in the viewer link. Markdown responses end with guidance for presenting Paperpile-style references.
All citation summaries use surname plus initials, retaining the first three and last two authors
when there are more than five.
resultCount counts returned matches, referenceCount counts distinct references on this page, and
total counts matching references across all pages when requested. count: "only" returns a total
without retrieving reference metadata or passages. limit and offset still page references and
only apply to a single query. The REST and SDK search response formats are unchanged.