parse-document

Parse Document

Use the dedicated document tools as the default interface. Do not fall back to manual lit CLI commands unless the user explicitly asks for the raw command line workflow or the extension tools are unavailable.

Tool routing

• Use document_parse to extract text or JSON from a local document.
• Use document_search to find a phrase and get page numbers plus bounding boxes for citations/source locations.
• Use document_screenshot to render pages as PNG image blocks when visual layout matters.

Recommended workflow for known text: document_search first, then document_screenshot only for relevant pages.

Efficient parsing

Choose the smallest useful output

• Use format: "text" when the user wants to read, summarize, quote, search, or review the document.
• Use format: "json" when the user needs structured page data, text positions, or bounding boxes.
• Avoid JSON unless coordinates or programmatic structure matter.

LiteParse v2 JSON output is shaped like:

{ "pages": [{ "pageNum": 1, "text": "...", "textItems": [] }], "text": "..." }

Limit scope early

If the task concerns only part of a document, pass targetPages instead of parsing everything.

Examples:

• a single chapter
• a cited appendix
• a page range from the user
• a specific page mentioned in an error report or screenshot request

Default maxPages is 1000, matching LiteParse v2.

Use OCR deliberately

• Use ocr: "off" for native-text PDFs when OCR is unnecessary.
• Leave OCR on automatic behavior for scanned PDFs or image-heavy documents.
• Use ocrLanguage for a single OCR language.
• Use ocrLanguages only when multilingual OCR is truly needed.
• Built-in Tesseract usually expects ISO 639-3 codes such as eng, deu, fra, or jpn.
• Many HTTP OCR servers instead expect ISO 639-1 codes such as en, de, fr, or ja.
• Increase dpi only when OCR quality or screenshot readability needs it.
• Use ocrServerUrl only when the user already has or wants an external OCR server.
• Use tessdataPath only for offline/air-gapped setups or custom Tesseract .traineddata files.

Password-protected documents

If parsing fails because a document is encrypted/password-protected, ask the user for the password and retry with password.

Search workflow

Use document_search when the user asks:

• where text appears
• for source/citation locations
• to find all mentions of a phrase
• to identify pages that should be inspected visually

Prefer targetPages when the relevant area is known. Use maxResults to cap broad searches.

Screenshot workflow

Use document_screenshot when text is not enough, for example:

• charts or figures
• handwriting/signatures
• dense tables
• visual page layout
• forms where spatial relationships matter

Keep screenshot page ranges small, usually one to four pages, unless the user explicitly asks for more.

document_parse also supports screenshotPages when parsing and screenshotting should happen together, but prefer the dedicated document_screenshot tool for visual-only follow-up.

Follow-up workflow

document_parse writes parsed output to temporary files and returns their paths. document_screenshot writes PNGs to temporary files and also returns image blocks.

After calling tools:

1. inspect returned parsed output paths with read when full content is needed
2. inspect returned screenshot paths with read when file-level visual review is needed
3. only copy files into the project if the user wants persistent artifacts

Do not inline an entire large document into context. Let the tool save the full result, then inspect selectively.

Removed LiteParse v1 options

Do not use these removed options:

• preciseBoundingBox
• preserveLayoutAlignmentAcrossPages

Alternatives:

• use format: "json" for LiteParse v2 textItems bounding boxes
• use document_search for phrase-level bounding boxes
• use document_screenshot for visual layout checks
• use targetPages to narrow extraction

Important constraints and expectations

• Office documents and spreadsheets may require LibreOffice on the host machine.
• Image inputs may require ImageMagick on the host machine.
• The tools surface missing dependencies as friendly errors; do not misdiagnose them as generic parser failures.
• Parsed outputs and screenshots are temporary by default. If the user wants durable files in the repo or a chosen folder, copy returned temp files afterward.
• The tools accept pi-style paths such as @relative/file.pdf and ~/Documents/file.pdf.

Good default patterns

Summarize or review a document

Use document_parse with:

• format: "text"
• targetPages if only part of the document matters
• ocr: "off" for clearly native-text PDFs

Then inspect the returned text file with read if needed.

Extract positions or bounding boxes

Use document_parse with:

• format: "json"
• targetPages when possible

Then inspect the JSON file with read.

Locate a phrase for citation

Use document_search with:

• phrase
• targetPages when possible
• maxResults for broad searches

Use returned page/bounding-box hits for citations or screenshot follow-up.

Review a visually complex page

Use document_screenshot with:

• pages for the relevant page range
• higher dpi only if readability is a problem

Parse a scanned or image-based document

Use document_parse with:

• OCR enabled
• ocrLanguage or ocrLanguages when the document language is known
• optionally higher dpi
• JSON only if positional data matters

Parameter reminders

High-value document_parse parameters:

• path
• format
• targetPages
• screenshotPages
• ocr
• ocrLanguage
• ocrLanguages
• ocrServerUrl
• numWorkers
• maxPages
• dpi
• preserveSmallText
• password
• tessdataPath

Prefer a minimal parameter set. Add advanced options only when the task clearly benefits from them.