Skip to main content
Glama
ni-c

freshrss-mcp

by ni-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Mark all as read

mark_all_as_read
DestructiveIdempotent

Marks all articles in a feed, category, label, or built-in stream as read, using a two-step confirmation token to avoid accidental irreversible changes.

Instructions

Marks every article of a feed, category, label or built-in stream as read. Two-step: the first call returns a confirmation token, the second call with that token performs the change. Which articles were unread before cannot be recovered afterwards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelNoUser label name exactly as returned by list_categories
streamNoBuilt-in stream: reading-list = everything (default), starred = favourites, main = feeds shown on the main stream, important = feeds marked important
feed_idNoNumeric feedId from list_feeds
categoryNoCategory (folder) name exactly as returned by list_categories
older_thanNoOnly articles published before this ISO-8601 date; default: all of them
confirm_tokenNoToken from the first call of this tool

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
streamYesWhich stream, in this server’s words.
olderThanYesThe cut-off that was applied.
markedAsReadYes

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 / label / maxLength
      Added value: +200
    • addedInput schema / properties / older_than / maxLength
      Added value: +64
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "markedAsRead": {
+      "const": true,
+      "type": "boolean"
+    },
+    "olderThan": {
+      "description": "The cut-off that was applied.",
+      "type": "string"
+    },
+    "stream": {
+      "description": "Which stream, in this server’s words.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "markedAsRead",
+    "stream",
+    "olderThan"
+  ],
+  "type": "object"
+}
  2. First observedv0.1.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate destructive and idempotent behavior; the description adds the irreversible nature and the confirm-token mechanism, making side effects clear.

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?

Two concise sentences cover purpose, action scope, confirmation requirement, and consequence without unnecessary detail.

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?

Provides sufficient context for a bulk mark-as-read operation, including token flow and irreversibility, though it does not elaborate on what the confirmation token payload looks like beyond the schema.

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?

All parameters are described with concrete details like exact source names, enum meanings, and default streams; however, interaction constraints between scope parameters are not spelled out.

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?

Clearly states the tool marks every article as read across a feed, category, label, or built-in stream, and distinguishes this bulk action from other scopes.

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?

Explains the two-step confirmation flow and optional older_than filter, but does not explicitly mention mutual exclusivity of scope parameters or when to prefer this tool over sibling mark_articles.

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