Skip to main content
Glama

Zotero Get Item Fulltext

zotero_get_item_fulltext

Extract and return the full text of a Zotero item's PDF or EPUB so the paper can be read; use for reading papers, not for searching or fetching metadata.

Instructions

Return the extracted text of an item's PDF or EPUB: most of the paper, often 10K+ tokens. Use it only when the user wants the paper READ, never to search (zotero_semantic_search, zotero_search_items) or for metadata (zotero_get_item_metadata); avoid reading several papers unless asked. item_key: normally the parent item, whose best attachment is picked (PDF first unless attachment_priority says otherwise); an attachment's own key reads exactly that file. PDFs stop at fulltext_display_max_pages (default 10), and a TRUNCATED heading names the pages read: continue with zotero_read_pdf_pages. Scanned PDFs without OCR may return little text.

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>"
    },
    "name": "zotero_get_item_fulltext"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

No annotations exist, so the description carries the full disclosure burden and does so: it warns of large token cost, documents the fulltext_display_max_pages default of 10, explains that a TRUNCATED heading names the pages read and points to zotero_read_pdf_pages for continuation, and flags that scanned PDFs without OCR return little text. These are non-obvious failure and cost characteristics an agent could not infer from the schema.

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 the core purpose and cost before the caveats, and every sentence adds real information. The heavy use of nested parentheticals makes it denser than necessary and slightly harder to scan, but no sentence is filler.

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?

For a single-parameter read tool with no output schema and no annotations, everything an agent needs is present: return content, size, truncation behavior, continuation path, and the OCR edge case. Nothing material is left to inference.

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

Parameters4/5

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

With 0% schema description coverage the description must compensate, and it largely does: it explains that item_key is normally the parent item, that the best attachment is chosen PDF-first, and that passing an attachment's own key reads exactly that file. The dangling reference to "attachment_priority" is not a parameter in this schema, leaving the agent unsure where that setting lives.

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?

Names a specific verb and resource ("Return the extracted text of an item's PDF or EPUB") and immediately scopes the output magnitude ("often 10K+ tokens"). It explicitly distinguishes itself from zotero_semantic_search, zotero_search_items and zotero_get_item_metadata, so an agent can route correctly without opening another schema.

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?

Gives an explicit positive condition ("only when the user wants the paper READ") plus two named exclusions for search and metadata with the sibling tools to use instead. It also adds a behavioral caution ("avoid reading several papers unless asked"), which is exactly the when-not guidance that prevents misuse.

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