Skip to main content
Glama

Remove feed

remove_feed
DestructiveIdempotent

Delete an RSS/Atom feed subscription and all stored entries by URL or feed ID. This clears the selected feed from the local SQLite database.

Instructions

Delete a subscription and all of its stored entries.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "remove_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoFeed URL to delete, if id is unknown
feed_idNoId of the feed to delete

Output Schema

NameRequiredDescriptionDefault
okYes
feedNoState of the feed after the call
messageYesHuman-readable summary of what happened
new_entriesNoEntries inserted by this call
discovered_fromNoHTML page the feed URL was auto-discovered on, if any
removed_entriesNoEntries deleted together with the feed

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered upstream. The description adds the non-obvious consequence — that all stored entries are deleted along with the subscription — which is exactly the kind of context annotations cannot express; it stops short of stating irreversibility or any confirmation requirement.

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?

A single front-loaded sentence with zero filler; the destructive scope is stated up front rather than buried. Nothing here could be removed without losing meaning.

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?

An output schema exists and annotations carry the safety semantics, so the description needn't explain returns or danger. However, for a destructive tool where zero parameters are required but at least one identifier is needed, it omits what happens on an empty call and whether deletion is recoverable.

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?

With 100% schema description coverage, both parameters are already documented, including the "if id is unknown" hint on url. The description adds nothing about the mutual exclusivity of url and feed_id or which wins if both are supplied, so baseline 3 applies.

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?

Specific verb plus resource ("Delete a subscription") with the important scope qualifier "and all of its stored entries". That cascade detail distinguishes it from a mere entry-clearing operation, though no sibling is named explicitly.

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?

No when-to-use, when-not-to-use, or alternative guidance is given. It never says whether to prefer this over, say, mark_entries for clearing data, or what to do for unsubscribing without deleting history.

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