Skip to main content
Glama
oscardvs

Zoteus

by oscardvs
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Hybrid

Annotate a PDF (highlights, notes)

zotero_annotate

Add or delete highlights, underlines, and notes in Zotero PDFs by quoting the passage—no page coordinates required.

Instructions

Add or delete Zotero PDF annotations (highlights, underlines, notes), the same objects you create in the Zotero PDF reader. action:"add" needs parent (a regular item key OR a PDF attachment key) and annotations: each with type (highlight|note|underline, default highlight), text (the exact passage to highlight), optional comment, color, page (0-based page index). You do not need page coordinates: give the passage in text and it is located in the PDF and anchored to the exact lines it occupies, so quoting a passage is enough to highlight it. Pass page to disambiguate a passage that repeats, or occurrence to pick among repeats; pass position ({"pageIndex":N,"rects":[[x1,y1,x2,y2],...]} in PDF points, bottom-left origin) only to place a highlight yourself. action:"delete" trashes the annotations in annotation_keys. Writes go to the running Zotero desktop app for your personal library (via its connector protocol, or its local-API writes where available), otherwise to the cloud Web API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNoDefault "add".
parentNoItem key or PDF attachment key to annotate.
library_idNo
annotationsNoAnnotations to add.
library_typeNo
annotation_keysNoAnnotation keys to trash (action:"delete").

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv1.9.0
    • addedInput schema / properties / annotations / items / properties / occurrence
      Added value: +{
+  "description": "Which occurrence of `text` to anchor when the passage appears more than once (1-based, in reading order). Only needed when a first attempt reports an ambiguous passage.",
+  "minimum": 1,
+  "type": "integer"
+}
    • changedInput schema / properties / annotations / items / properties / position / description
      Previous value: -"Zotero position: {\"pageIndex\": N, \"rects\": [[x1,y1,x2,y2],...]} (points, bottom-left origin), its JSON string, or shorthand [N, [x1,y1,x2,y2]]. Required for highlights/underlines to render in place."New value: +"Zotero position: {\"pageIndex\": N, \"rects\": [[x1,y1,x2,y2],...]} (points, bottom-left origin), its JSON string, or shorthand [N, [x1,y1,x2,y2]]. Optional: when omitted, the passage in `text` is located in the PDF and its coordinates are computed for you."
  2. Addedv1.3.1

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, the description discloses key behavioral traits: delete trashes annotations, text is located and anchored to exact lines without page coordinates, occurrence disambiguates repeated passages, and writes go to the running Zotero desktop app or fall back to the cloud Web API. No contradiction with the annotations is present.

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 long but dense and well organized. It front-loads the core operation, then highlights the most valuable guidance (no coordinates needed, occurrence, custom position), then deletion behavior and write routing. Every sentence carries practical information for invoking the tool correctly.

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 the tool's complexity, the description covers operation modes, required parent context, annotation types, ambiguity handling, and API routing. It does not describe the response shape or error behavior, and there is no output schema, but an agent still has enough information to construct a valid invocation.

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?

The description adds significant meaning beyond the 67%-coverage schema: it explains the difference between item keys and PDF attachment keys, defines text as the exact passage, notes that page is 0-based, and gives the position object format. It does not cover every parameter such as library_id or sort_index refiners, but the schema covers those adequately.

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 states a specific verb and resource: add or delete Zotero PDF annotations such as highlights, underlines, and notes. It also ties them to the objects created in the Zotero PDF reader, making the tool's intent precise and distinguishable from the sibling item, collection, and tag tools.

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 description gives clear usage context: annotate a PDF via a parent item key and annotation definitions, or delete annotations via annotation keys. It does not explicitly name sibling tools or state when not to use it, but the add/delete modes and required inputs make the intended use obvious.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/oscardvs/zoteus'

If you have feedback or need assistance with the MCP directory API, please join our Discord server