Skip to main content
Glama
ni-c

freshrss-mcp

by ni-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Import OPML

import_opml
Destructive

Imports RSS feeds from an OPML file, creating categories and refreshing all feeds. Two-step process: call once to get a confirmation token, then call again with that token to execute. No bulk undo.

Instructions

Subscribes to every feed in an OPML document, creating the categories it names, and then refreshes all feeds — which can take minutes on a large file. There is no bulk undo; every feed would have to be removed individually. Two-step: the first call returns a confirmation token, the second call with that token performs the import.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
opmlYesOPML document
confirm_tokenNoToken from the first call of this tool

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteYes
importedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "imported": {
+      "const": true,
+      "type": "boolean"
+    },
+    "note": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "imported",
+    "note"
+  ],
+  "type": "object"
+}
  2. First observedv0.1.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description goes beyond by explaining the nature of the destructiveness (no bulk undo), the time cost (minutes on large files), and the two-step confirmation mechanism. This adds substantial behavioral context not present in annotations.

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 three sentences with no waste. It front-loads the core action, then adds cautions and the two-step procedure. Every sentence contributes essential information without redundancy.

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?

For a tool with an output schema and strong annotations, the description covers all critical aspects: the action, side effects (refreshing), performance implication, undo limitation, and the required two-step call pattern. Nothing an agent needs to invoke it correctly is missing.

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 description coverage is 100% with clear parameter descriptions, so baseline is 3. The description adds meaning by explaining the confirm_token's role in the two-step process and clarifying that opml is processed to subscribe to every feed, enhancing the semantic understanding beyond the schema's brief descriptions.

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 states a specific verb ('Subscribes to every feed') and resource (OPML document), and adds distinctive details (creating categories, refreshing all feeds, two-step process). It clearly distinguishes itself from siblings like subscribe_feed (single feed) and export_opml (export) without ambiguity.

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?

The description gives a clear context: it's for bulk import via OPML, and it warns about the lack of bulk undo, implying caution. It does not explicitly reference alternatives, but the purpose is so specific that usage is obvious. The two-step instruction also guides the invocation sequence.

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