FeedKeeper RSS/Atom reader and remote MCP Server

Paginate items chronologically with cursors

list_items

Browse articles chronologically with cursor-based paging to move into older or newer history, filtering by date, feed, folder, unread, or bookmarked status.

Instructions

Lists articles chronologically with bidirectional cursor-based pagination. Use this tool for comprehensive browsing or historical paging through both read and unread articles. Pass nextCursor as 'before' to page backwards into older history, or newestCursor as 'after' to stream newly added items. Do NOT use for quick digests (use get_digest) or unread-only triage (use get_new_items).

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_items"
  }
}

Input Schema

Name	Required	Description
`after`	No	Cursor to fetch newer items (pass newestCursor from a previous page)
`limit`	No	Number of items to fetch per page (1 to 100, default: 20)
`since`	No	Filter for items published at or after this ISO date or date-time
`until`	No	Filter for items published at or before this ISO date or date-time
`before`	No	Cursor to fetch older items (pass nextCursor from a previous page)
`feedId`	No	Optional feed ID filter
`folderId`	No	Optional folder ID filter
`unreadOnly`	No	When true, only lists unread articles; default is false (all articles)
`bookmarkedOnly`	No	When true, only lists bookmarked articles

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv0.36.4Nov 9, 2026

addedInput schema / properties / after / description

Added value: +"Cursor to fetch newer items (pass newestCursor from a previous page)"

addedInput schema / properties / before / description

Added value: +"Cursor to fetch older items (pass nextCursor from a previous page)"

addedInput schema / properties / bookmarkedOnly / description
```
Added value: +"When true, only lists bookmarked articles"
```
addedInput schema / properties / feedId / description
```
Added value: +"Optional feed ID filter"
```
addedInput schema / properties / folderId / description
```
Added value: +"Optional folder ID filter"
```

addedInput schema / properties / limit / description

Added value: +"Number of items to fetch per page (1 to 100, default: 20)"

changedInput schema / properties / since / description

Previous value: -"Only items published at or after this ISO date or date-time"New value: +"Filter for items published at or after this ISO date or date-time"

addedInput schema / properties / unreadOnly / description

Added value: +"When true, only lists unread articles; default is false (all articles)"

changedInput schema / properties / until / description

Previous value: -"Only items published at or before this ISO date or date-time"New value: +"Filter for items published at or before this ISO date or date-time"

First observedv0.36.3Nov 9, 2026

TDQS

A4.3/5.0

Behavior4/5

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

No annotations are provided, so the description carries the disclosure burden; it establishes read semantics ('Lists') and explains the bidirectional cursor contract, including that nextCursor walks backwards into older history while newestCursor streams newer items — behavior the schema only states per-parameter. It stops short of disclosing cursor expiry, invalid-cursor behavior, or the shape of returned pages, which are the remaining gaps for an unannotated tool.

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?

Three sentences, front-loaded with purpose then mechanics then exclusions. Every clause carries routing or paging information; nothing is redundant with the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter tool with no annotations and no output schema, the description covers intent and paging but omits how the date/feed/folder/unread/bookmarked filters compose with cursor paging, and never states what a page returns beyond implicitly naming two cursor fields. Adequate for basic invocation, incomplete for the tool's full surface.

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 description coverage is 100%, so the baseline is 3; the description's added value is limited to linking output cursors (nextCursor/newestCursor) to the before/after inputs. It says nothing about the six filter parameters (since, until, feedId, folderId, unreadOnly, bookmarkedOnly) beyond a passing mention of 'read and unread articles'.

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?

States a specific verb and resource ('Lists articles chronologically') plus the distinguishing mechanism ('bidirectional cursor-based pagination'), and explicitly names the two siblings it is not (get_digest, get_new_items). No schema opening is required to know what this tool does.

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?

Gives explicit when-to-use ('comprehensive browsing or historical paging through both read and unread articles'), explicit when-not-to-use ('Do NOT use for quick digests', 'unread-only triage'), and names the alternative tool for each exclusion. It also spells out the two paging directions map to specific cursors.

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