zotero-library-mcp

Get Unfiled Items

get_unfiled_items

Read-onlyIdempotent

Retrieve unfiled items from your Zotero library that are not in any collection, with options to limit results and target specific libraries.

Instructions

Get items that are not in any collection (unfiled items).

Args: limit: Maximum number of items to return (default 25)

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
`limit`	No
`library_id`	No
`library_type`	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.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the selection criterion ("not in any collection") and the limit default, but does not disclose any other behavior such as pagination, ordering, or error conditions. This is acceptable given the annotations, but the description itself adds only limited behavioral context.

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 extremely concise: two sentences cover purpose and parameter usage with no filler. The purpose is stated first, followed by parameter details. Every word earns its place.

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?

For a read-only list tool with an output schema, the description is complete. It explains what the tool returns (unfiled items), the limit parameter, and the library targeting behavior. Nothing essential is missing for an agent to call it correctly.

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?

Schema description coverage is 0%, so the description must compensate. It explains limit as "Maximum number of items to return (default 25)" and clarifies that library_id and library_type must be used together or omitted. This adds crucial meaning beyond the bare schema, guiding correct invocation. It does not explain data types, but the schema already provides those.

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 the exact verb and resource: "Get items that are not in any collection (unfiled items)." It unambiguously defines what the tool does and is distinct from every sibling (e.g., get_recent_items, search_library).

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 provides clear usage instructions for the optional parameters: "Pass both library_id and library_type to target another library; omit both to use the configured default." This tells the agent exactly how to control scope. It does not explicitly mention when to choose this over alternatives, but no sibling covers the same use case, so the guidance is sufficient.

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