Skip to main content
Glama

rss_to_json

Convert RSS, Atom, or JSON Feed URLs or inline XML into clean JSON with items, dates, authors, summaries, categories, and enclosures. Filter by date, cap items, or discover feeds from HTML pages.

Instructions

RSS 2.0 / RSS 1.0 (RDF) / Atom / JSON Feed to clean JSON: feed title, link, language, updated, items with id, title, link, ISO dates, author, text summary, categories and enclosures (podcasts). URL or inline XML, item cap, since filter; HTML pages return discovered feed links. Costs 0.002 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rss_to_json"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoFeed URL
xmlNoInline feed (POST)
htmlNokeep HTML in summaries
limitNo1-100, default 20
sinceNoISO date: only newer items

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does so unusually well: it discloses the x402 pay-per-call model (0.002 USDC on Base), the authentication consequence (402 challenge without a payment key), and the HTML fallback behavior. Gaps remain around malformed/unsupported feed handling and non-payment errors, and the sentence 'HTML pages return discovered feed links' sits ambiguously next to an `html` parameter that means something else.

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?

Content is front-loaded: conversion scope and output shape first, then input modes and filters, then the pricing caveat. It is dense but each clause carries information; the field enumeration is long yet justified since no output schema exists.

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 five-parameter tool with no output schema and no annotations, the definition covers the return payload, input modes, filtering, and the payment/auth prerequisite, which is the critical operational detail. It could go one step further on failure modes and on the exact semantics of the `html` flag.

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 all five parameters and the baseline of 3 applies. The description restates URL/inline XML, item cap, and the `since` filter without adding format or constraint detail, and it never clarifies the `html` parameter ('keep HTML in summaries'), which the nearby HTML-page sentence could easily be confused with.

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 names a concrete transformation (RSS 2.0 / RSS 1.0 RDF / Atom / JSON Feed -> clean JSON) and enumerates the normalized output fields, so an agent knows exactly what the tool produces. It also distinguishes itself from the sibling list, which is dominated by validators and lookup tools with no feed-parsing overlap.

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?

It gives clear operating context: accept a URL or inline XML (POST), cap items, filter by `since`, and note that HTML pages return discovered feed links rather than failing. It stops short of explicit when-not guidance or naming an alternative path, but there is no obvious sibling competitor to route against.

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