Skip to main content
Glama

list_folders

Retrieve all RSS feed categories and folders from your FreshRSS instance to organize and manage your subscriptions.

Instructions

List all folders/categories

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The implementation of the 'list_folders' tool handler, which calls client.tags.list() and formats the output.
    wrapTool('list_folders', async () => {
      const { folders } = await client.tags.list();
    
      if (folders.length === 0) {
        return textResult('No folders found.');
      }
    
      const formatted = folders
        .map((f) => {
          const unread = f.unreadCount !== undefined ? ` (${f.unreadCount.toString()} unread)` : '';
          return `- ${f.name}${unread}`;
        })
        .join('\n');
    
      return textResult(formatted);
    })
  • Registration of the 'list_folders' tool in the MCP server.
    server.registerTool(
      'list_folders',
      {
        description: 'List all folders/categories',
        inputSchema: z.object({}).strict(),
      },
Behavior2/5

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

No annotations provided, so description carries full burden. While 'List' implies read-only behavior, the description lacks critical details: return format (IDs, names, objects?), pagination behavior, hierarchical structure, or whether empty folders are included.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely brief at 4 words, but appropriately sized for a simple parameterless operation. Front-loaded with verb first. No redundant filler, though bordering on under-specification.

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?

Given zero parameters and simple list semantics, description is minimally viable. However, lacks explanation of return values (critical since no output schema exists) and folder semantics within this feed management system.

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

Parameters4/5

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

Tool accepts zero parameters. Per scoring guidelines, baseline is 4 for parameterless tools. Schema coverage is vacuously 100% with empty properties object.

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?

Uses specific verb 'List' and identifies target resource 'folders/categories'. Distinguishes from siblings like list_labels and list_feeds by resource name, though could clarify what folders contain (feeds vs articles) to strengthen differentiation.

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?

Provides no guidance on when to use this versus list_labels, nor does it explain the relationship between folders and categories (synonyms or distinct?). No prerequisites or contextual conditions mentioned.

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