Skip to main content
Glama

Zotero Read Pdf Pages

zotero_read_pdf_pages

Reads selected pages of a Zotero item's PDF after an outline lookup, returning Markdown text or PNG page images for exact equations, figures, and tables; optionally crops a page region.

Instructions

Read chosen pages of an item's PDF, e.g. after zotero_get_pdf_outline. item_key: the paper or its PDF attachment. Reads start_page through end_page (1-indexed; omit end_page for one page). format='text' (default) returns Markdown and flags pages whose equations, figures or tables the text garbles; format='image' returns PNG page images (up to 10) to read those exactly. rect=[x, y, width, height] (normalized 0-1, e.g. from zotero_get_page_layout) returns just that region of start_page, zoomed in.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "item_key": "<item_key>",
      "start_page": "<start_page>"
    },
    "name": "zotero_read_pdf_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
rectNo
formatNotext
end_pageNo
item_keyYes
start_pageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden and does well: it discloses 1-indexing, the omit-end_page shorthand, that text mode returns Markdown and flags garbled content, that image mode caps at 10 PNGs, and that rect returns a zoomed region of start_page only. It does not mention failure modes (e.g., an item with no PDF attachment) or unit/efficiency limits for large page ranges.

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?

Front-loaded with purpose, then parameter-by-parameter fragments with zero filler. The colon-delimited telegraphic packing is dense and slightly harder to scan than prose would be, but no sentence is wasted.

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?

For a 5-parameter, no-annotation, no-output-schema tool, this covers inputs, output modes, and a key quality caveat. Remaining gaps are edge cases (interaction of rect with end_page, behavior on items lacking a PDF) rather than anything blocking a correct call.

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?

With 0% schema coverage across 5 parameters, the description compensates fully: item_key is defined as the paper or its PDF attachment, start_page/end_page are 1-indexed with the single-page shorthand, format's two enum values are explained with their distinct outputs, and rect is given its normalized 0-1 coordinate form plus provenance from zotero_get_page_layout. Every parameter gains meaning beyond the bare schema types.

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?

States a specific verb and resource ('Read chosen pages of an item's PDF') with clear scope, and distinguishes itself from siblings by naming the upstream tools (zotero_get_pdf_outline, zotero_get_page_layout) and their relationship. An agent can tell this apart from a fulltext or outline tool without opening the schema.

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?

Gives concrete workflow context ('after zotero_get_pdf_outline') and a decision rule between modes: text is the default, image is for pages where equations/figures/tables are garbled. It lacks an explicit exclusion against alternatives like zotero_get_item_fulltext, so it stops short of a full when/when-not statement.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.