Skip to main content
Glama
Sign In
mcp-zotero

mcp-zotero

by Xevos117
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_item_fulltext

Retrieve the full text of a Zotero item's indexed PDF to read complete papers instead of abstracts; supports PDFs indexed by Zotero desktop or imported attachments.

Instructions

Get the text of a Zotero item's stored PDF from Zotero's full-text index. Works for PDFs indexed by Zotero desktop and synced, or imported with import_pdf_to_zotero / find_and_attach_pdfs; not for linked URLs or web pages. Use this to read the full content of papers instead of relying on abstracts.

Input Schema

NameRequiredDescriptionDefault
item_keyYesItem key (the parent item or its PDF attachment), from search_library or get_collection_items
library_idNoNumeric user or group ID for this call (a group's ID is the number in its zotero.org/groups/<id> URL). Default: the configured library. Required with library_type 'group' when the server is configured for a user library.
library_typeNoLibrary for this call: 'user' (personal) or 'group'. Default: the library configured on the server.
max_charactersNoMaximum characters to return: a positive integer, or 0 for no limit (default: 50000); truncated: true in the result when cut

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv2.0.4
    • changedInput schema / properties / item_key / description
      Previous value: -"The Zotero item key (parent item or attachment key)"New value: +"Item key (the parent item or its PDF attachment), from search_library or get_collection_items"
    • changedInput schema / properties / library_id / description
      Previous value: -"Override the configured library ID for this call. Defaults to ZOTERO_LIBRARY_ID env (or ZOTERO_USER_ID). Required when library_type is 'group' and the server is configured for a user library."New value: +"Numeric user or group ID for this call (a group's ID is the number in its zotero.org/groups/<id> URL). Default: the configured library. Required with library_type 'group' when the server is configured for a user library."
    • changedInput schema / properties / library_type / description
      Previous value: -"Override the configured Zotero library type for this call. Defaults to ZOTERO_LIBRARY_TYPE env (or 'user'). Use to target a different library per call without restarting the server."New value: +"Library for this call: 'user' (personal) or 'group'. Default: the library configured on the server."
    • changedInput schema / properties / max_characters / description
      Previous value: -"Maximum characters to return (default: 50000, 0 = no limit)"New value: +"Maximum characters to return: a positive integer, or 0 for no limit (default: 50000); truncated: true in the result when cut"
    • addedInput schema / properties / max_characters / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / max_characters / minimum
      Added value: +0
    • changedInput schema / properties / max_characters / type
      Previous value: -"number"New value: +"integer"
  2. Changed3 schema fields changedv2.0.2
    • addedInput schema / properties / item_key / pattern
      Added value: +"^[23456789ABCDEFGHIJKLMNPQRSTUVWXYZ]{8}$"
    • addedInput schema / properties / library_id
      Added value: +{
+  "description": "Override the configured library ID for this call. Defaults to ZOTERO_LIBRARY_ID env (or ZOTERO_USER_ID). Required when library_type is 'group' and the server is configured for a user library.",
+  "pattern": "^\\d+$",
+  "type": "string"
+}
    • addedInput schema / properties / library_type
      Added value: +{
+  "description": "Override the configured Zotero library type for this call. Defaults to ZOTERO_LIBRARY_TYPE env (or 'user'). Use to target a different library per call without restarting the server.",
+  "enum": [
+    "user",
+    "group"
+  ],
+  "type": "string"
+}
  3. First observedv1.0.9

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well by disclosing the data source, coverage conditions, and a key limitation. It does not discuss authentication, rate limits, or detailed output shape, but the schema covers truncation via max_characters.

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 three efficient sentences with the purpose front-loaded, followed by scope and usage guidance. Every sentence contributes useful information without repetition.

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 read-only retrieval tool with full schema coverage but no output schema, the description sufficiently explains what is retrieved and the main limitations. It could be slightly more complete by explicitly describing the returned text/truncation behavior, though the max_characters schema description already covers truncation.

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?

The input schema has 100% description coverage for all four parameters, including item_key, library_id, library_type, and max_characters. The description adds context about the resource being read but does not add parameter-specific meaning beyond the schema, so the baseline of 3 is appropriate.

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 uses a specific verb and resource: getting the text of a Zotero item's stored PDF from Zotero's full-text index. It also clearly distinguishes the tool from related capabilities by saying it does not work for linked URLs or web pages.

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?

It gives clear usage context: use this to read full paper content instead of relying on abstracts. It also states an important exclusion, linked URLs and web pages, but does not explicitly name a sibling tool to use for those excluded cases.

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

Deploy Server

Other Tools