Skip to main content
Glama
ni-c

freshrss-mcp

by ni-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Update a feed

update_feed
DestructiveIdempotent

Rename a feed or move it to another category, creating the category if needed. Unspecified fields remain unchanged.

Instructions

Renames a feed and/or moves it to another category. A category that does not exist yet is created. Fields that are not given stay unchanged.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoNew title
feed_idYesNumeric feedId from list_feeds
categoryNoCategory to move the feed to

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
feedIdYes
updatedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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
    • 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"
+    },
+    "updated": {
+      "const": true,
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "feedId",
+    "updated"
+  ],
+  "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?

Beyond the annotations (destructive, idempotent), the description discloses important behaviors: automatic category creation and partial updates (fields not given remain unchanged), which are not captured elsewhere.

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 pack the main purpose and key behaviors. No fluff, well-structured, and easy to parse.

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?

With an output schema present and annotations for idempotency/destructive effects, the description covers all necessary operational details (what it does, partial updates, category creation). Nothing essential 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 descriptions already cover each parameter's meaning (title, feed_id, category). The description adds value by explaining that absent fields are left unchanged and that category creation happens automatically, enriching the parameter semantics.

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 tool renames a feed and/or moves it to another category, which is specific and distinct from sibling tools like rename_category_or_label or subscribe_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 clearly describes the action but does not explicitly contrast with alternatives (e.g., rename_category_or_label for category renames). The purpose is so clear that guidance is implied rather than stated.

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