FeedKeeper RSS/Atom reader and remote MCP Server

Delete a feed folder

delete_folder

Deletes a feed category folder while keeping subscribed feeds intact by moving them to the root level (unfiled).

Instructions

Deletes a feed category folder. Subscribed feeds inside the folder remain intact and are moved to the root level (unfiled). Destructive action for the folder organization. Returns { ok: true } on success.

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": {
      "folderId": "<folderId>"
    },
    "name": "delete_folder"
  }
}

Input Schema

Name	Required	Description	Default
`folderId`	Yes	The numeric ID of the folder to delete

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.36.4Nov 9, 2026
- addedInput schema / properties / folderId / description
```
Added value: +"The numeric ID of the folder to delete"
```
First observedv0.36.3Nov 9, 2026

TDQS

A3.8/5.0

Behavior4/5

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

No annotations are supplied, so the description carries the full burden: it discloses the non-obvious side effect that subscribed feeds are moved to root rather than deleted, labels the operation destructive for folder organization, and states the return shape { ok: true }. It omits error behavior for a nonexistent or invalid folderId, permission requirements, and whether any undo exists.

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 short sentences, front-loaded with the action, then the important side effect, then the return value. Every sentence contributes information and nothing is padded.

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?

For a one-parameter destructive tool with no annotations and no output schema, the description covers action, side effect, destructive nature, and success response. Error/failure semantics for a bad folderId are the only meaningful gap.

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 100% and the single parameter folderId is documented there with type and minimum constraints. The description adds no additional meaning about the ID (format, source, where to obtain it), which is the baseline expectation when the schema already does the documentation.

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?

"Deletes a feed category folder" gives a specific verb and a clearly-scoped resource, which separates it from rename_folder and create_folder. It stops short of naming a sibling or the condition that picks this over other folder operations, so it is clear but not maximally differentiated.

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?

Usage is implied by the resource itself (removing a folder) and the description usefully states the consequence for contained feeds, but there is no explicit when-to-use versus alternatives, no prerequisite such as the folder needing to exist, and no guidance on what to do with feeds first.

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