Skip to main content
Glama

Read the items of an RSS or Atom feed

feed
Read-only

Items of an RSS, Atom or RDF feed, or of the feed a web page advertises: title, link, published date, author and a 300-character summary, newest first (max 50). since keeps items published on or after a date. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": "feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFeed address, or a web page that advertises one
limitNo1 to 50 (default 20)
sinceNoOnly items published on or after this date, e.g. 2026-09-01

Output Schema

NameRequiredDescriptionDefault
urlNo
feedNo
countNo
itemsNo
sinceNo
sourceNo
checkedAtNo
totalInFeedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Goes well past the readOnlyHint/openWorldHint annotations: it discloses the 50-item cap, newest-first ordering, 300-character summary truncation, the since-date filter behavior, and a full billing model (per successful call, x402/USDC, failed calls free). Cost and truncation are exactly the behavioral facts an agent cannot infer from structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the returned fields and scope, then constraints, then price; each clause carries information. The opening sentence is long and comma-stacked, so a reader must parse carefully, but no sentence is filler.

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?

Output schema exists, so the field listing is somewhat redundant, yet limits, ordering and payment are all covered. The only gap is failure behavior for non-feed URLs, which matters because a page without an advertised feed is a likely input.

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%, so the schema already documents url, limit and since. The description mostly restates those ('since keeps items published on or after a date', 'max 50') without adding format or edge-case detail beyond the schema; baseline 3 applies.

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 ('Items of an RSS, Atom or RDF feed, or of the feed a web page advertises') plus exactly which fields come back. The accepted input scope (feed URL or advertising web page) makes it distinguishable from a generic page reader like 'read'.

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

Usage Guidelines3/5

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

Implied usage is clear: call it with a feed URL when you want parsed entries. But there is no explicit when-to-use or when-not guidance, no mention of what to do when the URL turns out not to advertise a feed, and no named alternative for plain-page extraction.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources