FeedKeeper RSS/Atom reader and remote MCP Server

Get subscribed feed details

get_feed

Inspect a single subscribed feed by numeric ID to retrieve its metadata, subscription settings, polling health status, and unread count for troubleshooting and review.

Instructions

Returns metadata, subscription settings, polling health status, and unread count for a single subscribed feed by its numeric feed ID. Safe read-only operation. Use list_feeds to view all subscribed feeds.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "feedId": "<feedId>"
    },
    "name": "get_feed"
  }
}

Input Schema

Name	Required	Description	Default
`feedId`	Yes	The numeric ID of the subscribed feed to inspect

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.36.4Nov 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it explicitly declares 'Safe read-only operation,' which is the single most important behavioral fact for a mutating-API-adjacent surface. It also discloses the returned content categories. It does not mention behavior for invalid or unsubscribed feed IDs, which is the remaining gap.

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, front-loaded with what is returned, followed by the safety property and the sibling routing. No filler and nothing repeated.

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 single-parameter read-only getter with no output schema, the description compensates well by enumerating the return categories (metadata, settings, polling health, unread count). Only error/invalid-ID behavior is absent, which is minor for this complexity level.

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?

With one parameter at 100% schema coverage, the schema already documents feedId as the numeric ID of a subscribed feed to inspect; the description adds only the 'numeric' and 'subscribed' qualifiers, which the schema largely implies. Baseline 3 applies since the schema does the heavy lifting.

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 (Returns) and resource (a single subscribed feed by numeric ID) and enumerates exactly what comes back: metadata, subscription settings, polling health status, unread count. This is clearly distinguishable from list_feeds and update_feed without opening any schema.

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

Usage Guidelines4/5

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

The final sentence routes the agent: use list_feeds to view all subscribed feeds, implying this tool is for inspecting one feed when its ID is known. That is a clear usage signal, though no explicit exclusions (e.g., what to use for unsubscribed or discovered feeds) or prerequisites are given.

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