Skip to main content
Glama

fetch

Retrieve a Zotero item by its key and get its full text, title, URL, and metadata in a JSON envelope.

Instructions

ChatGPT custom connector FETCH endpoint — name is REQUIRED by the MCP-over-web spec (see platform.openai.com/docs/mcp); do not rename. Not intended for general MCP clients — in Claude or other regular MCP contexts use zotero_get_item_fulltext and zotero_get_item_metadata, which return richer markdown. Retrieves a single Zotero item and returns a JSON envelope {"id","title","text","url","metadata":{...}} matching the ChatGPT connector citation viewer. id: an 8-char Zotero item key — typically from a previous search call. Blank/missing returns an empty envelope (no error). url field: Zotero web-library URL when ZOTERO_LIBRARY_ID is set; otherwise a zotero://select/items/ deep-link. text field: extracted fulltext via the same path as zotero_get_item_fulltext; if none can be extracted, falls back to title + authors + abstract so the connector isn't blank. metadata field: itemType, date, DOI, authors, tags, both URLs. SILENT FALLBACK: errors return an envelope with {"metadata":{"error":…}} rather than raising, to keep the ChatGPT connector stable. Example (agent-invoked): fetch(id='RTKZQI8E').

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided, but description fully covers behavior: silent fallback on errors (returns error envelope instead of raising), fallback for text extraction, URL construction logic, and handling of blank id. Describes return format in detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is detailed and front-loaded with purpose and context. Every sentence adds value, though slightly verbose. Could be shortened without losing clarity, but still well-structured.

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 the output schema exists (though not shown), the description still explains return values in detail. Differentiates from over 30 sibling tools with specific guidance. Covers error cases and edge cases. Highly complete.

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 has 0% description coverage, but description adds meaning: id is an 8-char Zotero item key from previous search. Provides example value. No other parameters.

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 it retrieves a single Zotero item for the ChatGPT connector, with specific verb ('fetch') and resource ('single Zotero item'). It distinguishes from siblings by noting that in other contexts, zotero_get_item_fulltext and zotero_get_item_metadata should be used.

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?

Explicitly states when not to use: 'Not intended for general MCP clients — in Claude or other regular MCP contexts use zotero_get_item_fulltext and zotero_get_item_metadata'. Provides an example invocation and explains behavior with blank/missing id.

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