Skip to main content
Glama

unsubscribe

Remove an RSS feed subscription from your FreshRSS instance by specifying the feed ID to stop receiving updates.

Instructions

Unsubscribe from an RSS feed

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
feedIdYesID of the feed to unsubscribe from

Implementation Reference

  • The 'unsubscribe' tool implementation that registers the tool and defines the handler logic using `wrapTool`.
    server.registerTool(
      'unsubscribe',
      {
        description: 'Unsubscribe from an RSS feed',
        inputSchema: unsubscribeSchema,
      },
      wrapTool('unsubscribe', async (args: z.infer<typeof unsubscribeSchema>) => {
        await client.feeds.unsubscribe(args.feedId);
        return textResult(`Successfully unsubscribed from feed ${args.feedId}`);
      })
    );
  • The schema definition for the 'unsubscribe' tool input.
    export const unsubscribeSchema = z
      .object({
        feedId: z.string().describe('ID of the feed to unsubscribe from'),
      })
      .strict();
Behavior2/5

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

No annotations provided, so description carries full burden. Fails to disclose whether this permanently deletes the feed and its articles, merely stops updates, or is reversible. Doesn't mention authentication requirements or rate limits.

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 concise at 4 words with no filler. Front-loaded with the action verb. However, 'appropriately sized' is debatable given the lack of behavioral transparency, though that's penalized in other dimensions.

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?

Inadequate for a state-modifying tool with no annotations. Missing crucial context: what happens to existing articles, whether the operation is destructive, success/failure indicators, and relationship to the subscribe sibling tool.

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 ('ID of the feed to unsubscribe from'), so baseline is 3. Description adds no additional semantic context about the parameter format, validation rules, or how to obtain valid feed IDs.

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?

States a specific verb (unsubscribe) and resource (RSS feed). Clear enough to distinguish from sibling 'subscribe' by virtue of being the inverse operation, though it doesn't explicitly contrast with other feed management tools like delete_folder or edit_feed.

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 versus alternatives, prerequisites (e.g., verifying feed exists), or side effects. Doesn't mention that feedId should likely come from list_feeds or that subscribe is the reverse operation.

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