Skip to main content
Glama

Read RSS/Atom Feed

read_rss
Read-onlyIdempotent

Fetch and parse RSS or Atom feeds to retrieve recent items from news sites, blogs, podcasts, and release feeds. Returns title, link, date, and summary for each entry.

Instructions

Fetch and parse an RSS or Atom feed, returning the latest items. Use for news sites, blogs, podcasts and release feeds — cheaper and more current than web_search when you know the feed.

Args:

Returns items as { title, link, date, summary }.

Example: { "url": "https://lwn.net/headlines/rss", "limit": 5 }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesRSS or Atom feed URL
limitNoMax items
Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint, etc. The description adds context about being cheaper and more current, and explains the return structure, but no contradictions or additional behavioral quirks are disclosed.

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?

Very concise: two sentences for purpose, bullet list for args/returns, and an example. No wasted words.

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

Completeness5/5

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

Despite no output schema, the description fully explains return fields and provides an example. Parameters are well-documented, and use case guidance is clear. The tool is simple and completely covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds a concrete example, notes the default limit, and explains the return shape, providing value beyond the schema.

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 it fetches and parses RSS/Atom feeds, specifies use cases (news, blogs, podcasts, release feeds), and differentiates from sibling web_search by noting it's cheaper and more current when the feed URL is known.

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 states when to use (for known feeds) and contrasts with web_search, giving clear guidance on alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/highercomve/mcptools'

If you have feedback or need assistance with the MCP directory API, please join our Discord server