Skip to main content
Glama
SamMorrowDrums

reMarkable MCP Server

remarkable_read

Read-onlyIdempotent

Extract text, annotations, or raw content from reMarkable documents with pagination to manage context. Search with regex and enable OCR for handwritten notes.

Instructions

Read and extract text content from a reMarkable document. Extracts content from a document with pagination to preserve context window.

Content types:

  • "text" (default): Full extracted text (PDF/EPUB content + annotations)

  • "raw": Original PDF/EPUB text only (no annotations). Works in every transport, as long as the source file is present (very large PDFs/EPUBs may not be synced to the cloud).

  • "annotations": Only annotations, highlights, and handwritten notes

Use pagination to read large documents without overwhelming context:

  • Start with page=1 (default)

  • Check "more" field - if true, there's more content

  • Use "next_page" value to get the next page

  • "total_pages" is the physical document count; "content_pages" is the extracted-text count used by page/more/next_page

  • "total_pages_known" reports whether the physical count was available. Raw PDF reads count the downloaded PDF directly. If a raw EPUB archive cannot be read, content still returns with total_pages=null.

  • If older USB firmware returns only a native PDF, "text" returns source text without annotations and "annotations" reports that the archive is unavailable instead of trying to parse the PDF as a zip.

Use grep to search for specific content on the current page.

OCR uses Google Vision when configured, otherwise Tesseract.

  • document: Document name or path (use remarkable_browse to find documents)

  • content_type: "text" (full), "raw" (PDF/EPUB only), "annotations" (notes only)

  • page: Extracted-content page number (default: 1). Physical document pages are reported separately as total_pages.

  • grep: Optional regex pattern to filter content (searches current page)

  • include_ocr: Enable handwriting OCR for annotations (default: False)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
grepNo
pageNo
documentYes
include_ocrNo
content_typeNotext

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds rich behavioral detail: pagination mechanics (more, next_page, total_pages, content_pages, total_pages_known), content-specific behavior (text, raw, annotations), handling of older USB firmware, OCR provider fallback, and grep filtering. No contradictions with annotations. The description fully complements the safety profile.

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?

The description is long but well-structured with XML-like tags (usecase, instructions, parameters, examples). It is front-loaded with the core purpose. Every section serves a purpose: pagination details avoid context overflow, parameter explanations prevent misuse, examples show typical invocations. Could be slightly more concise by merging the <instructions> bullet on pagination into fewer sentences, but the organization makes it easy to scan.

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 the tool's complexity (5 parameters, pagination, content types, OCR, firmware edge cases), the description is thorough. It explains output fields like more, next_page, total_pages, content_pages, total_pages_known – and since an output schema exists, it doesn't need to enumerate all return values. It is slightly incomplete on error handling (what if document not found?) and does not mention rate limits or authentication requirements, but these may be covered externally. Overall, it leaves little ambiguity for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage, so the <parameters> section in the description carries the full burden. It explains each parameter with clear semantic meaning: 'document' (name or path, use browse to find), 'content_type' (list of options with outcomes), 'page' (extracted-content page vs physical pages), 'grep' (regex on current page), 'include_ocr' (handwriting OCR). The examples further illustrate parameter usage. This adds significant value beyond the raw 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 opens with a clear '<usecase>Read and extract text content from a reMarkable document.' This specifies a concrete verb and resource. The three content types ('text', 'raw', 'annotations') further clarify what is returned. The tool is well-distinguished from siblings like 'remarkable_image' (image extraction), 'remarkable_export' (export as file), and 'remarkable_search' (search across documents).

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

Usage Guidelines3/5

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

The description provides detailed instructions on pagination and grep filtering but does not explicitly state when to use this tool over its siblings. For example, it does not contrast with 'remarkable_export' or 'remarkable_image' for specific use cases. The parameter section advises using 'remarkable_browse to find documents', which implies a prerequisite, but it lacks explicit 'when/when-not' guidance.

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/SamMorrowDrums/remarkable-mcp'

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