Skip to main content
Glama
freshrss-mcp

freshrss-mcp

by hrsather

freshrss_unsubscribe

Destructive

Unsubscribe from a feed and delete its stored articles. Set confirm=true to perform the destructive removal.

Instructions

Unsubscribe from a feed, deleting its articles. Requires confirm=true.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "feed": "<feed>"
    },
    "name": "freshrss_unsubscribe"
  }
}

Input Schema

NameRequiredDescriptionDefault
feedYes
confirmNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, so the agent knows this is a mutation. The description adds value beyond them by disclosing the blast radius ('deleting its articles') and an invocation requirement ('confirm=true') that the schema alone only hints at via a default-false boolean. It stops short of saying whether deletion is reversible or how failures surface.

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 short clauses with zero filler; the destructive consequence is front-loaded before the precondition. Every phrase earns its place.

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?

With an output schema present and annotations covering the safety profile, the description supplies the two missing behavioral facts: article deletion and the confirm requirement. The remaining gap is the unresolved format of the required 'feed' argument, which matters given 0% schema coverage.

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 description coverage is 0%, so the description must carry the load. It explains the 'confirm' parameter's required value, which is genuinely useful since the schema shows only a default of false. It says nothing about the required 'feed' parameter — whether it takes an ID, URL, or stream ID — leaving the most important input ambiguous.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Unsubscribe from a feed') plus the consequence ('deleting its articles'), so the agent knows exactly what operation this performs. It does not name any sibling (e.g. freshrss_edit_feed or freshrss_delete_category) to differentiate, which keeps it short of a 5.

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?

'Requires confirm=true' is a concrete operational precondition that shapes how the tool must be invoked. However, there is no guidance on when to prefer this over siblings such as freshrss_edit_feed, or when not to unsubscribe at all — usage is implied rather than explained.

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