zotero-library-mcp

Get Item Fulltext

get_item_fulltext

Read-onlyIdempotent

Extract readable, bounded plain text from a Zotero item's PDF or full-text index, with optional attachment selection and max character limit; returns text directly without temporary file paths.

Instructions

Get bounded plain text from a paper's PDF or Zotero full-text index.

Unlike download_pdf, this returns readable text directly and never exposes a server-local temporary path.

Args: item_key: The Zotero item key (the parent item, not the attachment) attachment_key: Optional PDF attachment key when an item has several PDFs max_chars: Maximum number of characters to return (1,000-200,000)

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": "get_item_fulltext"
  }
}

Input Schema

Name	Required	Description	Default
`item_key`	Yes
`max_chars`	No
`library_id`	No
`library_type`	No
`attachment_key`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.10.0Sep 14, 2026

addedInput schema / properties / library_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Library Id"
+}

addedInput schema / properties / library_type

Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "user",
+        "group"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Library Type"
+}

First observedv0.9.0Aug 12, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description still adds real behavioral context: output is bounded by max_chars and no server-local temp path is exposed. It omits behavior when no PDF/full-text exists, but that is minor.

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 purpose, then a differentiating sentence, then an Args block. Efficient and readable, though the Args listing partially duplicates what the schema already structures.

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?

An output schema exists so return-value explanation is unnecessary, and annotations cover the safety profile. The description is complete enough to call the tool correctly, with the only gaps being the two undocumented library parameters and the no-PDF case.

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

Parameters3/5

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

Schema coverage is 0%, so the description carries the full burden. It documents item_key (parent not attachment), attachment_key (for multiple PDFs), and max_chars (1,000-200,000), which is meaningful added value, but library_id and library_type are left entirely undocumented in both schema and description.

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 (get) and resource (bounded plain text from a paper's PDF or Zotero full-text index), and explicitly differentiates itself from the sibling download_pdf. An agent can identify what this returns 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?

The contrast with download_pdf ('returns readable text directly and never exposes a server-local temporary path') gives clear guidance on when to prefer this tool. It does not, however, address when to use this vs. search_fulltext, which also touches full-text content.

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