Skip to main content
Glama

subscribe

Add new RSS feeds to your FreshRSS instance by providing the feed URL, with options to set a custom title and organize into categories.

Instructions

Subscribe to a new RSS feed

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL of the RSS/Atom feed
titleNoCustom title for the feed
categoryNoCategory/folder to add the feed to

Implementation Reference

  • Registration and MCP tool handler for the 'subscribe' tool.
    server.registerTool(
      'subscribe',
      {
        description: 'Subscribe to a new RSS feed',
        inputSchema: subscribeSchema,
      },
      wrapTool('subscribe', async (args: z.infer<typeof subscribeSchema>) => {
        await client.feeds.subscribe(args.url, args.title, args.category);
        return textResult(`Successfully subscribed to ${args.url}`);
      })
    );
  • Core implementation of the 'subscribe' operation in the FeedService.
     * Subscribe to a new feed
     */
    async subscribe(feedUrl: string, title?: string, category?: string): Promise<void> {
      const body: Record<string, string> = {
        ac: 'subscribe',
        s: `feed/${feedUrl}`,
      };
      if (title !== undefined && title !== '') body.t = title;
      if (category !== undefined && category !== '') body.a = `user/-/label/${category}`;
    
      await this.http.post('/reader/api/0/subscription/edit', body);
    }
  • Input schema definition for the 'subscribe' tool.
    export const subscribeSchema = z
      .object({
        url: z.string().url().describe('URL of the RSS/Atom feed'),
        title: z.string().optional().describe('Custom title for the feed'),
        category: z.string().optional().describe('Category/folder to add the feed to'),
      })
      .strict();
Behavior2/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 but offers minimal information. It implies state mutation (creating a subscription) but does not clarify side effects like immediate article fetching, duplicate handling, or failure modes.

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?

The single sentence is efficiently structured with the action front-loaded. However, at only five words, it is arguably too terse given the tool's mutative nature and the presence of similar sibling tools, leaving room for one clarifying sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a state-mutating tool with no annotations and no output schema, the description is insufficient. It lacks critical context such as confirmation of what the operation returns, error conditions, or whether the subscription persists immediately.

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 input schema has 100% description coverage for all three parameters (url, title, category). Since the schema fully documents the parameters, the baseline score applies even though the description adds no additional semantic context beyond the schema.

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 provides a clear verb ('Subscribe') and resource ('RSS feed'), making the basic purpose understandable. However, it fails to differentiate from the sibling tool 'quickadd_feed', which likely performs a similar function.

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 guidance is provided on when to use this tool versus alternatives like 'quickadd_feed', nor are prerequisites mentioned (e.g., verifying the feed URL is accessible). The description offers no selection 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