Skip to main content
Glama

edit_feed

Modify RSS feed subscriptions by updating titles or organizing them into different categories within FreshRSS.

Instructions

Edit a feed subscription (rename or move to different category)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
feedIdYesID of the feed to edit
titleNoNew title for the feed
categoryNoNew category/folder for the feed

Implementation Reference

  • Handler implementation for the edit_feed tool, which updates a feed's title and category using the FreshRSS client.
    server.registerTool(
      'edit_feed',
      {
        description: 'Edit a feed subscription (rename or move to different category)',
        inputSchema: editFeedSchema,
      },
      wrapTool('edit_feed', async (args: z.infer<typeof editFeedSchema>) => {
        await client.feeds.edit(args.feedId, args.title, args.category);
        return textResult(`Successfully updated feed ${args.feedId}`);
      })
    );
  • Zod schema definition for the edit_feed tool input parameters.
    export const editFeedSchema = z
      .object({
        feedId: z.string().describe('ID of the feed to edit'),
        title: z.string().optional().describe('New title for the feed'),
        category: z.string().optional().describe('New category/folder for the feed'),
      })
      .strict();
Behavior2/5

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

With no annotations provided, the description carries full burden but lacks disclosure of error behavior (invalid feedId), whether both title and category can be updated atomically in one call, or side effects like URL preservation. Only states the two possible operations without behavioral context.

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?

Single sentence of 8 words with zero redundancy. Main clause states the action, parenthetical efficiently specifies the two modification modes. Every element earns its place.

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?

Adequate for a simple metadata-update tool with complete schema coverage, but gaps remain regarding partial update semantics, error scenarios, and confirmation of whether both parameters can be provided simultaneously given no output schema or annotations.

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%, establishing baseline 3. The description maps conceptual operations ('rename'→title, 'move'→category) but adds no syntax details, format constraints, or examples beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses specific verb 'Edit' with resource 'feed subscription' and parenthetically clarifies the two supported operations (rename/move), clearly distinguishing it from siblings like 'subscribe' (create), 'unsubscribe' (delete), and 'rename_folder' (different resource).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies usage for existing feeds through the word 'Edit', but provides no explicit when-to-use guidance contrasting with 'subscribe' for new feeds or 'unsubscribe' for removal, nor mentions that feedId must reference an existing subscription.

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