Skip to main content
Glama
Sign In
FeedKeeper RSS/Atom reader and remote MCP Server

FeedKeeper RSS/Atom reader and remote MCP Server

by visualfusion
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Discover feeds on a website

discover_feeds

Scan a website URL to discover available RSS, Atom, and JSON feed links and titles without subscribing. Use the returned candidate URLs to choose a feed to subscribe to.

Instructions

Inspects a website URL and discovers available RSS, Atom, and JSON feed links from HTML link tags. Safe read-only operation: does NOT subscribe to any feed. Returns a list of discovered candidate feed URLs and titles. Use subscribe_feed to subscribe to one of the discovered URLs.

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": {
      "url": "<url>"
    },
    "name": "discover_feeds"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe website URL to scan for available RSS/Atom feed links

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.36.4
    • changedInput schema / properties / url / description
      Previous value: -"The website URL to discover feeds from"New value: +"The website URL to scan for available RSS/Atom feed links"
  2. First observedv0.36.3

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 does the work of declaring read-only semantics and that no subscription side effect occurs, plus it sketches the return value (list of candidate URLs and titles). The remaining gap is edge-case behavior: whether an empty result is an empty list or an error, and whether it performs a live network fetch with any timeout/rate constraints.

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?

Four short sentences with no redundancy: capability, safety constraint, return shape, and next-step sibling are each stated once in a sensible order.

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, and the description compensates by naming what comes back (URLs and titles). For a single-parameter read tool this is nearly complete; only failure/empty-result behavior is left unspecified.

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 `url` parameter is already documented as the site to scan, so the description adds little beyond it. It does not clarify whether a feed URL (rather than a site URL) is acceptable input, which would have been genuine added meaning.

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?

"Inspects a website URL and discovers available RSS, Atom, and JSON feed links from HTML link tags" gives a specific verb (discovers), a specific resource (feed links), and the exact mechanism (HTML link tags). This clearly separates it from list_feeds (existing subscriptions) and subscribe_feed (mutation on a known URL).

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 routes the agent: "Use subscribe_feed to subscribe to one of the discovered URLs." It also states the negative case ("does NOT subscribe to any feed"), so the boundary between discovery and subscription is unambiguous.

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

Deploy Server

Other Tools