feed-reader-mcp

Fetch multiple feeds

fetch_many

Fetch multiple RSS/Atom feeds and combine them into a single date-sorted list of recent items. Build a digest from various sources.

Instructions

Fetch several RSS/Atom feeds and return a merged, date-sorted list of recent items. Useful for building a digest.

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": {
      "urls": "<urls>"
    },
    "name": "fetch_many"
  }
}

Input Schema

Name	Required	Description	Default
`urls`	Yes	List of feed URLs.
`perFeed`	No	Maximum items to take from each feed.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 7, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description must disclose behavior. It mentions the merged, date-sorted output but does not cover failure modes, network errors, or partial feed handling. This is minimal but not entirely bare.

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?

Two sentences with the main action front-loaded and no redundant phrasing. Each sentence carries useful information.

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?

The tool has a low complexity (2 params) and the schema fully documents parameters. The description explains the returned data (merged, date-sorted list) but does not specify item structure, which would be helpful given no output schema. Still, it is adequate for tool selection.

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?

The schema covers 100% of parameters with descriptions ('List of feed URLs', 'Maximum items to take from each feed'), so the baseline is 3. The description adds no extra parameter detail beyond what the schema provides.

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?

The description clearly states the tool fetches multiple RSS/Atom feeds and returns a merged, date-sorted list, distinguishing it from the sibling tool fetch_feed for single feeds. The verb 'Fetch' and resource 'feeds' are specific.

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 description provides context for use ('Useful for building a digest') and implies it is for multiple feeds by using 'several'. However, it does not explicitly contrast with fetch_feed or state when not to use it.

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

Deploy Server