Skip to main content
Glama

list_bookmarks

Browse Instapaper bookmarks by folder or search results and set a limit to retrieve unread, archived, or starred articles for your reading list.

Instructions

List bookmarks from a specific folder or search results. Retrieve unread, archived, or starred articles with optional limit. This is the primary way to browse your reading list. Supports filtering by folder, limit, and sync parameters for efficient bulk data retrieval.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_bookmarks"
  }
}

Input Schema

NameRequiredDescriptionDefault
haveNoOptional: comma-separated bookmark IDs you already have for sync optimization
limitNoMaximum number of bookmarks to return (1-500, default 25)
folderNoFolder to list from: "unread" (default), "archive", "starred", or a folder_id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose a meaningful default (folder defaults to unread) and that ``have`` exists for sync optimization, but it omits return ordering, pagination/bulk semantics, and any read-only or side-effect statement for what is evidently a read tool.

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

Conciseness3/5

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

The purpose is front-loaded, but four sentences contain noticeable redundancy: "optional limit" appears twice and the unread/archived/starred enumeration duplicates the folder schema description. Tightening to two sentences would lose nothing.

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?

For a simple, zero-required-parameter read tool with a fully described schema and no output schema, the definition covers purpose, defaults, and the main filters adequately. The only real gap is routing against the search sibling and the semantics of the sync-oriented ``have`` parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so all three parameters are already documented with ranges, defaults, and accepted values. The description only echoes those concepts (folder filtering, optional limit, sync parameters) without adding format or behavioral detail, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("List bookmarks") and names the scoping axis (folder or search results), so an agent can tell it is a read/list operation. However, "or search results" blurs the line with the sibling search_bookmarks, which the description never names or disambiguates.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"This is the primary way to browse your reading list" gives an implied default-use signal, and the folder parameter hints at the unread/archive/starred cases. There is no explicit when-to-use vs. search_bookmarks, list_highlights, or the bulk move/archive tools, so the agent must infer the boundary itself.

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