FeedKeeper RSS/Atom reader and remote MCP Server

List subscribed feeds

list_feeds

Lists your subscribed RSS/Atom feeds with unread counts, subscription settings, and polling health; filter to show only feeds with poll errors.

Instructions

Lists all RSS/Atom feeds the current user is subscribed to, including subscription settings, unread counts, and polling health status. Safe read-only operation. To inspect a single feed in detail, use get_feed. To discover new feeds, use discover_feeds.

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

Input Schema

Name	Required	Description	Default
`onlyWithErrors`	No	When true, only returns feeds whose last poll failed or that have consecutive errors

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.36.4Nov 9, 2026

changedInput schema / properties / onlyWithErrors / description

Previous value: -"Only return feeds whose last poll failed"New value: +"When true, only returns feeds whose last poll failed or that have consecutive errors"

First observedv0.36.3Nov 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations supplied, the description carries the safety burden itself by declaring 'Safe read-only operation', and it goes further by disclosing the returned fields including polling health. It does not state whether the result set is paginated or bounded, nor any auth/permission requirements, which are the remaining behavioral gaps for a list 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 short sentences, zero filler: capability first, safety second, sibling routing last. Every sentence earns its place and the key scoping information is front-loaded.

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?

No output schema exists, so the description must describe return values — and it does, listing subscription settings, unread counts, and polling health. The only shortfall is that it never hints at the error-filtering capability, leaving that entirely to the schema.

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% and the single optional parameter onlyWithErrors is fully documented in the schema. The description adds no filtering semantics of its own, so the baseline of 3 applies — the schema does all the work here.

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 all RSS/Atom feeds the current user is subscribed to') and enumerates what the listing carries: subscription settings, unread counts, and polling health. The scope ('subscribed') is enough to separate it from discover_feeds and get_feed without opening either schema.

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?

Names both alternatives and the condition that selects each: get_feed for single-feed detail, discover_feeds for finding new feeds. An agent has an explicit routing rule for the three closely related tools.

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