Skip to main content
Glama
rss-mcp

rss-mcp

by huangcheng

remove_subscription

Deletes an RSS or Atom subscription and removes its cached entries using the subscription ID, keeping your feed list and local database clean.

Instructions

Delete a subscription and its cached entries.

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": {
      "subscription_id": "<subscription_id>"
    },
    "name": "remove_subscription"
  }
}

Input Schema

NameRequiredDescriptionDefault
subscription_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It usefully states that cached entries are also deleted, which is important context beyond the bare action. However, it does not address irreversibility, required permissions, or what happens to entries that reference the subscription.

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 a single front-loaded sentence with no wasted words. It communicates the primary action and an important side effect efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple and has only one parameter, and an output schema exists so return values need not be explained. However, because this is a destructive operation with no annotations, the description should say more about permanence, permissions, or error behavior. It is minimally adequate but leaves meaningful gaps.

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

Parameters2/5

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

The tool has one required parameter, subscription_id, and schema description coverage is 0%. The description does not explain what the ID refers to, where to obtain it, or whether it is the same ID used by list_subscriptions. The parameter name is somewhat self-explanatory, but the description adds no meaning beyond the schema.

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?

The description states a specific verb and resource: 'Delete a subscription.' It also adds a side effect, 'and its cached entries,' which clarifies the scope of deletion. It is clearly distinct from the add_subscription sibling, though it does not explicitly name alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives such as list_subscriptions or mark_entry. The destructive nature is implied by 'Delete,' but no prerequisites, confirmation, or when-not-to-use conditions are given.

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