freshrss-mcp

Overview Schema Source Related Servers Discussions Admin

Unsubscribe from a feed

unsubscribe_feed

DestructiveIdempotent

Delete an RSS feed and all its stored articles, read state, and stars. First call returns a confirmation token; second call completes deletion permanently.

Instructions

Deletes a feed together with all of its stored articles, read state and stars. Two-step: the first call returns a confirmation token, the second call with that token performs the deletion. This cannot be undone — re-subscribing starts from whatever the feed currently offers.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`feed_id`	Yes	Numeric feedId from list_feeds
`confirm_token`	No	Token from the first call of this tool

Output Schema

TableJSON Schema

Name	Required	Description	Default
`feedId`	Yes
`unsubscribed`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.3.2Sep 8, 2026

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": {
+    "feedId": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "unsubscribed": {
+      "const": true,
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "feedId",
+    "unsubscribed"
+  ],
+  "type": "object"
+}

First observedv0.1.1Aug 18, 2026

TDQS

A5/5.0

Behavior5/5

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

The description discloses the destructive nature (deletes feed and associated data), irreversibility ('cannot be undone'), and the two-step behavior, going beyond the annotations by specifying exactly what will be removed.

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 concise (three sentences) and front-loads the core action before explaining the two-step process and consequences. No unnecessary words or redundancies.

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?

It covers the essential context: what is deleted, how to confirm, and the irreversible outcome. Since the output schema exists and is not described, that omission is acceptable. The description leaves no critical gaps for an agent to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Both parameters (feed_id and confirm_token) are described with sources: 'Numeric feedId from list_feeds' and 'Token from the first call of this tool.' This fully clarifies their meaning and usage, achieving 100% schema coverage.

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 action ('Deletes a feed') and the scope ('together with all of its stored articles, read state and stars'), making it distinct from sibling operations like subscribe 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 Guidelines5/5

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

It explains the two-step confirmation process explicitly: 'first call returns a confirmation token, the second call with that token performs the deletion.' This gives clear guidance on how to use the tool correctly.

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

Deploy Server