Skip to main content
Glama

delete_folder

Remove a folder or category from FreshRSS to organize your RSS feeds, automatically moving contained feeds to the default location.

Instructions

Delete a folder/category (feeds will be moved to default)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the folder/label to delete

Implementation Reference

  • The handler implementation for the delete_folder tool.
    wrapTool('delete_folder', async (args: z.infer<typeof deleteTagSchema>) => {
      await client.tags.delete(args.name);
      return textResult(`Deleted folder "${args.name}".`);
    })
  • Registration of the delete_folder tool.
    server.registerTool(
      'delete_folder',
      {
        description: 'Delete a folder/category (feeds will be moved to default)',
        inputSchema: deleteTagSchema,
      },
      wrapTool('delete_folder', async (args: z.infer<typeof deleteTagSchema>) => {
        await client.tags.delete(args.name);
        return textResult(`Deleted folder "${args.name}".`);
      })
    );
  • Zod schema definition for the delete_folder tool input.
    export const deleteTagSchema = z
      .object({
        name: z.string().describe('Name of the folder/label to delete'),
      })
      .strict();
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses the critical side effect that feeds are moved to default rather than deleted, but omits other behavioral traits like reversibility, idempotency, permission requirements, or error conditions.

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?

Single sentence with action front-loaded ('Delete a folder/category') and critical side effect in efficient parenthetical. Zero waste; every word earns its place for a simple 1-parameter tool.

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?

Appropriate for a simple destructive operation with 100% schema coverage. The description addresses the essential user concern (what happens to feeds?) but could strengthen completeness by noting irreversibility or error cases given the lack of annotations.

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 has 100% description coverage ('Name of the folder/label to delete'), establishing baseline 3. The description doesn't add syntax details, format constraints, or examples beyond what the schema provides.

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?

Clear verb 'Delete' and resource 'folder/category'. The parenthetical '(feeds will be moved to default)' clarifies scope and side effects. Distinguishes from label operations via 'folder/category' terminology but doesn't explicitly contrast with sibling 'delete_label'.

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?

No explicit when-to-use vs alternatives (e.g., rename_folder), but the side effect disclosure '(feeds will be moved to default)' implicitly guides usage by clarifying data preservation behavior. Lacks explicit exclusions or prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alysson-souza/freshrss-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server