Skip to main content
Glama
ni-c

freshrss-mcp

by ni-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Subscribe to a feed

subscribe_feed

Subscribe to an RSS feed by providing a feed or website URL; FreshRSS discovers the feed and creates the category if needed.

Instructions

Subscribes to a feed. The URL may point at the feed itself or at a website — FreshRSS discovers the feed and then downloads it, so this call can take a while. A category that does not exist yet is created.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesFeed URL or website URL (http/https)
titleNoTitle to use instead of the feed's own title
categoryNoCategory to file the feed under; created if unknown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteYes
feedIdYes
subscribedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.3.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / category / maxLength
      Added value: +200
    • addedInput schema / properties / title / maxLength
      Added value: +1000
    • addedInput schema / properties / url / maxLength
      Added value: +8192
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "feedId": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "note": {
+      "type": "string"
+    },
+    "subscribed": {
+      "const": true,
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "feedId",
+    "subscribed",
+    "note"
+  ],
+  "type": "object"
+}
  2. First observedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

The description discloses side effects: it creates a category if it does not exist, and it performs network operations that may be slow. This aligns with the annotations (readOnlyHint false, openWorldHint true, idempotentHint false) and does not contradict them. It does not mention all possible side effects but covers the key ones.

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 two sentences, front-loading the main purpose and then providing necessary behavioral details. No fluff or repetition. It is well-structured and easy to parse.

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 description sufficiently covers the purpose, input flexibility, side effects, and latency. It does not describe the return value, but an output schema is indicated, so that is not required. Overall, it gives enough context for an agent to decide when and how to use it.

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?

The input schema already covers all three parameters (url, title, category) with descriptions. The description adds meaning to the 'category' parameter by explaining that a missing category is created. It does not add extra detail for 'url' or 'title' beyond the schema, but the coverage is complete.

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 primary purpose: 'Subscribes to a feed.' It also clarifies the input flexibility (URL may be a feed or website) and that a category is created if needed, which distinguishes it from read-only or management tools like list_feeds or update_feed.

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 provides practical guidance on when to use this tool: when you have a URL that might be a website or feed, and it warns that the call can take a while due to discovery and download. It does not explicitly contrast with sibling tools but the context is sufficient.

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

Deploy Server

Other Tools