FeedKeeper RSS/Atom reader and remote MCP Server

Create a feed folder

create_folder

Create a category folder to organize feed subscriptions, then assign feeds to it with move_feed_to_folder.

Instructions

Creates a new category folder to organize feed subscriptions. Requires write scope. Returns the created folder object with its assigned id, name, and position. Folders can be assigned to feeds using move_feed_to_folder.

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

Input Schema

Name	Required	Description	Default
`name`	Yes	The unique display name for the new folder (1 to 100 characters)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.36.4Nov 9, 2026
- addedInput schema / properties / name / description
```
Added value: +"The unique display name for the new folder (1 to 100 characters)"
```
First observedv0.36.3Nov 9, 2026

TDQS

A4/5.0

Behavior4/5

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

No annotations are supplied, so the description has to cover all behavioral disclosure, and it does a fair job: it names the required scope and describes exactly what the call returns (id, name, position). It does not say how the tool behaves when the name already exists, even though the schema calls the name "unique," and that name reuse is the main failure mode for this kind of creation.

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?

Every sentence has a purpose: purpose, auth requirement, return shape, and sibling cross-reference, all in about four short sentences. The most important information (what the tool creates) is stated first.

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?

Because the tool has no output schema, describing the returned object (id, name, position) is genuinely useful. For a one-parameter creation tool, the definition is nearly complete; only the behavior on duplicate names is missing.

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?

The tool takes one parameter, and schema description coverage is 100%; the schema already documents the name, including its 1-100 character bounds. The description adds the idea of a "category folder" but no new detail about how to format or constrain the name, so it stays at the baseline.

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 gives a specific verb and resource: "Creates a new category folder to organize feed subscriptions." That verb naturally separates it from siblings like list_folders, rename_folder, and delete_folder, though the description never explicitly names those alternatives.

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?

It states a prerequisite ("Requires write scope") and points to the natural follow-up action ("Folders can be assigned to feeds using move_feed_to_folder"). It stops short of explicit exclusions, such as checking list_folders first to avoid creating a duplicate folder.

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