Skip to main content
Glama
ni-c

freshrss-mcp

by ni-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete a category or label

delete_category_or_label
DestructiveIdempotent

Delete a category or user label from FreshRSS. First call returns a confirmation token; second call with that token completes the deletion.

Instructions

Deletes a category (its feeds move to the default category, no articles are lost) or a user label (it is detached from every article). FreshRSS matches categories first, so a category and a label of the same name cannot be told apart here. Two-step: the first call returns a confirmation token, the second call with that token performs the deletion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName, exactly as in list_categories
confirm_tokenNoToken from the first call of this tool

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
deletedYes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already mark destructiveHint=true and idempotentHint=true, but the description adds significant behavioral detail beyond that: it explains that deleting a category moves feeds to the default category without losing articles, that labels are detached from articles, that FreshRSS prioritizes categories, and that a two-step confirmation token process is required. This goes well beyond the structured metadata and provides critical operational context.

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 compact and well-structured, front-loading the primary purpose, then the behavioral details, and finally the two-step mechanism. Every sentence adds necessary information without redundancy or fluff. It is easy to parse and directly actionable.

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 description covers all essential aspects for correct invocation: what is deleted, consequences for feeds/articles, the naming ambiguity, and the confirmation flow. Since an output schema exists, return values are already documented. There is no missing information that would prevent an agent from calling the tool correctly.

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?

Both parameters have descriptions in the schema (100% coverage), so the schema already explains what 'name' and 'confirm_token' mean. The description adds no extra parameter-level semantics beyond restating that the name must match list_categories and that the token comes from the first call, both of which are already in the schema. Thus, a baseline score 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 action (deletes a category or label), specifies the exact effects on feeds and articles, and distinguishes between the two entity types. It also explains the two-step process, which is essential for correct usage. This clearly differentiates it from siblings like rename_category_or_label and unsubscribe_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?

The description provides clear context about when to use the tool (to delete a category or label) and the two-step flow. However, it does not explicitly name alternatives or state conditions for when not to use it. The caution about categories and labels sharing names is a useful guideline, but no direct comparison with sibling tools is given, so a 4 is appropriate.

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