Skip to main content
Glama

Rss2json

by io.github.pipeworx-io

Feed

feed
Read-onlyIdempotent

Fetch RSS/Atom feed as JSON.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoMax items to return. Applied locally when no api_key is supplied (rss2json only honours it for keyed callers), so it always works.
api_keyNoOptional free rss2json API key for higher limits.
rss_urlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
feedNoFeed metadata
itemsNoArray of feed items/entries
statusNoStatus of the API response (ok, error, etc.)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / properties / count / description
      Added value: +"Max items to return. Applied locally when no api_key is supplied (rss2json only honours it for keyed callers), so it always works."
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "rss_url": "https://feeds.arstechnica.com/arstechnica/index"
+  },
+  {
+    "api_key": "your-rss2json-api-key",
+    "count": 10,
+    "rss_url": "https://www.bbc.com/news/rss.xml"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "feed": {
+      "description": "Feed metadata",
+      "properties": {
+        "description": {
+          "description": "Feed description",
+          "type": "string"
+        },
+        "image": {
+          "description": "Feed image URL",
+          "type": "string"
+        },
+        "link": {
+          "description": "Feed link",
+          "type": "string"
+        },
+        "title": {
+          "description": "Feed title",
+          "type": "string"
+        },
+        "url": {
+          "description": "Feed URL",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "items": {
+      "description": "Array of feed items/entries",
+      "items": {
+        "properties": {
+          "author": {
+            "description": "Item author",
+            "type": "string"
+          },
+          "categories": {
+            "description": "Item categories",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "content": {
+            "description": "Full item content",
+            "type": "string"
+          },
+          "description": {
+            "description": "Item description or content",
+            "type": "string"
+          },
+          "enclosure": {
+            "description": "Media enclosure (podcast, video, etc.)",
+            "properties": {
+              "length": {
+                "description": "Enclosure size in bytes",
+                "type": "string"
+              },
+              "link": {
+                "description": "Enclosure URL",
+                "type": "string"
+              },
+              "type": {
+                "description": "MIME type",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "link": {
+            "description": "Item URL",
+            "type": "string"
+          },
+          "pubDate": {
+            "description": "Publication date in ISO 8601 format",
+            "type": "string"
+          },
+          "title": {
+            "description": "Item title",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "status": {
+      "description": "Status of the API response (ok, error, etc.)",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds that both RSS and Atom formats are supported, which is useful, but discloses no further behavioral traits like rate limits or error handling.

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?

The description is a single, focused sentence front-loading the action and output format. Every word earns its place with no fluff.

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 is simple, and with an output schema present and strong annotations, the description is sufficient. It states the feed types supported and output format, covering the core context without needing extra detail.

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 67% (count and api_key have descriptions, rss_url does not). The tool description does not add any parameter-level meaning beyond what the schema already provides, but the required rss_url is self-explanatory.

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 'Fetch RSS/Atom feed as JSON' clearly states the verb (fetch), the resource (RSS/Atom feed), and the output format (JSON). It distinguishes from all sibling tools, none of which mention feed handling.

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?

The description implies usage for retrieving RSS/Atom feeds, but provides no explicit when-to-use or when-not-to-use guidance, and names no alternatives. The context is clear but not elaborated.

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

All Rss2json toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.3/5.0
Disambiguation2/5

Many tools serve overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all query Pipeworx data in similar ways. Polymarket tools also heavily overlap. This leads to ambiguity for an agent trying to select the right tool.

Naming Consistency2/5

Tool names are inconsistent, mixing snake_case (ai_visibility_check), all lowercase (feed, forget), and underscore-separated verbs (ask_pipeworx_grounded, list_subscriptions). No consistent pattern is followed.

Tool Count2/5

With 32 tools, the server feels overloaded for its stated purpose of RSS-to-JSON conversion. Many tools are unrelated (e.g., prediction markets, entity profiles, memory) making the scope too broad for a focused server.

Completeness2/5

The tool set has notable gaps: only one RSS-related tool (feed), and missing basic operations like creating or updating entities. The heavy focus on Pipeworx and Polymarket leaves the core domain underserved.

Resources