Skip to main content
Glama

list_feeds

Retrieve all subscribed RSS feeds from your FreshRSS instance to manage your feed collection.

Instructions

List all subscribed RSS feeds

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The implementation of the `list_feeds` tool handler, which fetches the list of feeds via the client and formats it for output.
    wrapTool('list_feeds', async () => {
      const feeds = await client.feeds.list();
    
      if (feeds.length === 0) {
        return textResult('No feeds subscribed.');
      }
    
      const formatted = feeds
        .map((f) => {
          const category = f.categoryName !== '' ? ` [${f.categoryName}]` : '';
          return `- ${f.title}${category}\n  URL: ${f.url}\n  ID: ${f.id}`;
        })
        .join('\n\n');
    
      return textResult(formatted);
    })
  • The registration of the `list_feeds` tool within the MCP server using `registerTool`.
    server.registerTool(
      'list_feeds',
      {
        description: 'List all subscribed RSS feeds',
        inputSchema: z.object({}).strict(),
      },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'List' implying a read-only operation, but fails to describe the return format, pagination behavior, or what properties are included for each feed (titles, URLs, IDs).

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?

The description consists of a single, efficient sentence with zero redundant words. It is appropriately front-loaded with the action and scope immediately clear.

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 the tool's simplicity (zero parameters) and lack of output schema, the description adequately covers the basic operation but leaves significant gaps regarding the structure and content of the returned feed data. For an unannotated tool without output schema, more detail on return values would be expected for a higher score.

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?

The input schema contains zero parameters, which establishes a baseline score of 4 per the evaluation rules. The description correctly implies no filtering is possible by stating 'all' feeds will be returned.

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 uses a specific verb ('List') and resource ('subscribed RSS feeds') that clearly distinguishes this from sibling tools like list_articles, list_folders, or list_labels. However, it stops short of being fully comprehensive by not clarifying what constitutes a 'feed' in this context (e.g., URLs, metadata, etc.).

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?

The description provides no guidance on when to use this tool versus alternatives. While the tool name is descriptive, there is no explicit mention of prerequisites, ordering constraints (e.g., check existence first), or exclusion criteria.

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