Zotero-MCP

Overview Schema Source Related Servers Discussions Admin

zotero_get_fulltext

Retrieve the indexed full text of a PDF attachment in Zotero using its attachment item key. The attachment must be indexed.

Instructions

Read the indexed full text of an attachment (usually a PDF).

Zotero must have indexed the attachment. Pass an attachment key, not the parent reference key -- use zotero_get_item to find it.

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_fulltext"
  }
}

Input Schema

Name	Required	Description	Default
`item_key`	Yes
`max_chars`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 31, 2026

TDQS

A4.1/5.0

Behavior3/5

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

No annotations are provided, so the description must disclose behavioral traits. It clearly indicates a read-only operation via 'Read' and adds a key prerequisite ('must have indexed'), but it does not describe error behavior or what happens if the attachment isn't indexed, leaving some transparency gaps.

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 two concise sentences, front-loaded with the main purpose. Each sentence adds essential context (what it reads and how to provide the correct key), with no redundant or extraneous content.

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?

Given that an output schema exists, the description does not need to detail return values. It covers the core function, prerequisite, and the critical attachment-key distinction, but omits max_chars semantics and error behavior, making it adequate yet not fully comprehensive.

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

Parameters2/5

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

Schema description coverage is 0%, and the description only clarifies that 'item_key' must be an attachment key, not a parent key. It does not explain the 'max_chars' parameter at all, leaving its semantics and interaction with the tool unexplained.

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 clearly states the tool's function: 'Read the indexed full text of an attachment (usually a PDF).' The verb 'Read' and resource 'indexed full text' are specific, and the tool is distinguished from siblings by explicitly requiring an attachment key and referencing zotero_get_item.

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 provides explicit guidance: it states the prerequisite that Zotero must have indexed the attachment, and instructs to pass an attachment key rather than the parent reference key, directing users to zotero_get_item for finding the correct key. This gives clear when-to-use and alternative tool information.

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