Skip to main content
Glama
ni-c

freshrss-mcp

by ni-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Rename a category or label

rename_category_or_label
DestructiveIdempotent

Renames a category or label in FreshRSS, preserving all associated feeds and articles.

Instructions

Renames a category (folder) or a user label. FreshRSS resolves the name against its categories first and falls back to labels, so one tool covers both. Feeds and articles keep their assignment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesCurrent name, exactly as in list_categories
new_nameYesNew name

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYes
fromYes
renamedYes

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 / name / maxLength
      Added value: +200
    • addedInput schema / properties / new_name / maxLength
      Added value: +200
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "from": {
+      "type": "string"
+    },
+    "renamed": {
+      "const": true,
+      "type": "boolean"
+    },
+    "to": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "renamed",
+    "from",
+    "to"
+  ],
+  "type": "object"
+}
  2. First observedv0.1.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already carry destructiveHint=true and idempotentHint=true. The description adds valuable context: the resolution order and that feeds/articles keep their assignment, which clarifies what is and is not affected. No contradiction with 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?

Three concise sentences: the first states the action, the second explains the resolution behavior, and the third notes the side-effect. Every sentence adds value with no 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?

The tool is simple, has only 2 well-documented parameters, an output schema exists, and annotations cover safety and idempotency. The description covers behavior and side-effects, leaving nothing essential missing.

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

Parameters3/5

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

Schema coverage is 100% and both parameters are described with concrete details (e.g., 'exactly as in list_categories'). The description adds no new parameter-specific information beyond the schema, so the baseline of 3 is appropriate.

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 verb 'Renames' and the resource 'category (folder) or user label', and specifies the resolution order (categories first, then labels). This distinguishes it from sibling tools like delete_category_or_label and clarifies the single-tool coverage.

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 explains that one tool covers both categories and labels, implying it is the sole rename operation. It does not explicitly name alternatives or exclusions, but the context is clear enough for an agent to decide when to use it.

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