Skip to main content
Glama

quickadd_feed

Add a website or feed URL to FreshRSS; the system automatically detects and subscribes to the actual RSS feed.

Instructions

Quick-add a feed URL; FreshRSS will detect the actual feed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesWebsite or feed URL to quick-add

Implementation Reference

  • The handler implementation for 'quickadd_feed', which uses the client to perform the operation.
    wrapTool('quickadd_feed', async (args: z.infer<typeof quickaddSchema>) => {
      await client.feeds.quickadd(args.url);
      return textResult(`Quick-added feed from ${args.url}`);
    })
  • The registration of the 'quickadd_feed' tool with the MCP server.
    server.registerTool(
      'quickadd_feed',
      {
        description: 'Quick-add a feed URL; FreshRSS will detect the actual feed.',
        inputSchema: quickaddSchema,
      },
      wrapTool('quickadd_feed', async (args: z.infer<typeof quickaddSchema>) => {
        await client.feeds.quickadd(args.url);
        return textResult(`Quick-added feed from ${args.url}`);
      })
    );
  • Input schema definition for the 'quickadd_feed' tool.
    export const quickaddSchema = z
      .object({
        url: z.string().url().describe('Website or feed URL to quick-add'),
      })
      .strict();
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It successfully explains the auto-detection mechanism ('detect the actual feed'), but omits whether the operation is idempotent, what happens if the feed already exists, or what the tool returns upon success.

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 is a single, efficient sentence of 12 words with zero redundancy. It front-loads the action and immediately follows with the mechanism, demonstrating optimal information density.

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 single-parameter, simple operation with no output schema, the description covers the core mechanism adequately. However, it lacks guidance on the relationship to 'subscribe' and does not indicate whether the tool returns the newly created feed ID or confirmation status.

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% ('Website or feed URL to quick-add'), so the schema fully documents the parameter. The description reinforces that the URL can be either a website or direct feed, but adds no additional semantic detail 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?

The description uses a specific verb ('Quick-add') and resource ('feed URL'), and distinguishes itself from siblings via the 'FreshRSS will detect the actual feed' clause, implying auto-discovery functionality that differs from manual subscription methods.

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?

No explicit when-to-use or when-not-to-use guidance is provided. The sibling tool 'subscribe' likely offers an alternative subscription method, but the description fails to clarify which tool to use for manual vs. automatic feed addition.

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