Related Servers

Most tools are clearly separated, aided by exceptionally thorough descriptions that cross-reference sibling tools (e.g., add_tags/remove_tags/set_tags vs rename_tag; download_attachment vs get_fulltext; trash_item vs delete_item_permanently). The main ambiguity risk is the cluster of metadata-discovery tools—list_item_fields, list_item_type_fields, list_item_creator_types, list_creator_fields—whose subtle boundaries could cause misselection, and the update_item/update_publication_status pair where one is a special case of the other.

The set consistently follows snake_case verb_noun conventions: list_* for reads, create_*/update_*/delete_* for lifecycle operations, and add_*/remove_*/set_* for granular edits. Minor deviations include upload_attachment (which breaks the create_* pattern used by create_note/create_item), the asymmetric restore_from_trash vs trash_item pair, and the verbose move_item_to_different_library.

At 39 tools, the surface is well beyond the 25+ threshold, even though Zotero's domain is genuinely complex. The count is inflated by five metadata-listing tools (list_item_types, list_item_fields, list_item_type_fields, list_item_creator_types, list_creator_fields) and five tag-related tools that could plausibly be consolidated into fewer, more general introspection and tag-management tools.

Lifecycle coverage is strong: items have full CRUD plus trash/restore/permanent-delete and cross-library move; collections, notes, attachments, and tags all have appropriate creation, mutation, and deletion paths. The notable gap is saved searches, which have create/list/delete but no update tool, forcing delete-and-recreate workflows; attachment metadata updates also lack a dedicated tool, though update_item likely covers them since attachments are items.