zotero-library-mcp

Get Item Fulltext

get_item_fulltext

Read-onlyIdempotent

Retrieve bounded plain text from a paper's PDF or Zotero full-text index for a given item key. Returns readable text directly, avoiding server-local temporary 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)

Pass both library_id and library_type to target another library; omit both to use the configured default.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON 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.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral detail beyond annotations: the result is bounded plain text, sourced from either PDF or full-text index, and it never exposes a server-local temporary path. This is more than the minimum but does not describe edge cases like what happens when no full-text is available.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and well-structured. The main purpose is front-loaded, the download_pdf contrast is one sentence, and the parameter explanations are terse but complete. Every sentence earns its place with no filler or redundant restating of the tool name.

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?

Given the output schema exists and annotations cover safety, the description covers everything an agent needs to select and invoke this tool correctly: what it returns, how it differs from a key sibling, all parameter semantics, and library selection rules. There are no significant missing behavioral or parameter details.

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?

Schema description coverage is 0%, so the description carries the full burden of explaining parameters. It does so thoroughly: item_key is clarified as the parent item rather than the attachment, attachment_key is marked optional for multi-PDF items, max_chars has a concrete range (1,000-200,000), and library_id/library_type pairing behavior is specified. This is exactly the semantic enrichment the schema lacks.

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 specific action and resource: 'Get bounded plain text from a paper's PDF or Zotero full-text index.' It immediately differentiates from download_pdf by noting it returns readable text directly and avoids exposing a server-local temporary path. This makes the tool's identity unmistakable among many siblings.

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?

The description explicitly contrasts this tool with download_pdf, telling the agent when this is the better choice. It also gives a clear rule for library targeting: 'Pass both library_id and library_type to target another library; omit both to use the configured default.' This is actionable selection and usage guidance.

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