Skip to main content
Glama

zotero_create_area_annotation

Create a rectangular annotation on a specific PDF page to highlight figures, diagrams, or tables. Specify page number and normalized coordinates for the rectangle.

Instructions

Create a PDF AREA/IMAGE annotation — a rectangle drawn on an arbitrary page region (figures, diagrams, tables, non-text content). For highlighting selectable text, use zotero_create_annotation instead. attachment_key: PDF attachment key — NOT the parent item key (use zotero_get_item_children to find attachments). page: 1-indexed page number (page 1 is the first page). x, y: top-left corner in NORMALIZED page coordinates in [0, 1] — (0, 0) is the page's top-left, (1, 1) is the bottom-right. width, height: rectangle size, also normalized to [0, 1] and relative to the page (not to x, y). comment: optional note attached to the annotation. color: hex color (default '#ffd400' yellow). Scope: PDFs only — EPUB attachments are NOT supported. Requires a writable library (web API key or hybrid mode) — fails in local-only mode. Example: zotero_create_area_annotation(attachment_key='NHZFE5A7', page=7, x=0.15, y=0.22, width=0.6, height=0.35, comment='Figure 3 — mean completion rates').

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
attachment_keyYesPDF attachment key (e.g., "NHZFE5A7")
pageYes1-indexed PDF page number
xYesNormalized left coordinate (0..1)
yYesNormalized top coordinate (0..1)
widthYesNormalized width (0..1)
heightYesNormalized height (0..1)
commentNoOptional comment on the annotation
colorNoAnnotation color in hex format#ffd400
tagsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Behavioral traits are well explained: coordinate normalization (0..1, top-left origin), 1-indexed page numbers, failure in local-only mode, and scope (PDF only). The description compensates for missing annotations with these details.

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 well-structured: purpose first, then parameter explanations, scope, requirements, and example. No redundant sentences; every sentence adds information.

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 9 parameters and an output schema, the description covers all necessary aspects: parameter details, constraints, requirements, and a usage example. It is complete for an agent to use the tool correctly.

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 coverage is high (89%), and the description adds significant value: clarifies coordinate system, explains width/height are relative to page, provides example with real values, and distinguishes attachment_key from parent item key.

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 creates a PDF area/image annotation (rectangle on arbitrary page region). It explicitly distinguishes from the sibling zotero_create_annotation for text highlighting, providing a specific verb and resource.

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 gives explicit when-to-use guidance (non-text content vs. text), directs to an alternative tool (zotero_create_annotation), and states limitations (PDF only, not EPUB, requires writable library). It also explains how to find the correct attachment key.

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/54yyyu/zotero-mcp'

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