Skip to main content
Glama

rename_folder

Change the name of a folder or category in your FreshRSS feed reader by specifying the current and new names.

Instructions

Rename a folder/category

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
oldNameYesCurrent name of the folder/label
newNameYesNew name for the folder/label

Implementation Reference

  • Implementation and registration of the 'rename_folder' tool in the registerTagTools function.
    server.registerTool(
      'rename_folder',
      {
        description: 'Rename a folder/category',
        inputSchema: renameTagSchema,
      },
      wrapTool('rename_folder', async (args: z.infer<typeof renameTagSchema>) => {
        await client.tags.rename(args.oldName, args.newName);
        return textResult(`Renamed folder "${args.oldName}" to "${args.newName}".`);
      })
    );
  • Schema definition for renaming folders or labels.
    export const renameTagSchema = z
      .object({
        oldName: z.string().describe('Current name of the folder/label'),
        newName: z.string().describe('New name for the folder/label'),
      })
      .strict();
Behavior2/5

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

No annotations are provided, and the description carries the full burden of behavioral disclosure. It fails to indicate whether the operation is idempotent, what happens if 'newName' already exists, or whether this is a destructive operation that affects nested feeds/articles.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely brief (four words), which borders on under-specification rather than efficient conciseness. While it contains no wasted words, it lacks the necessary detail to be genuinely useful for tool selection.

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 mutation tool with no annotations and no output schema, the description is inadequate. It lacks behavioral constraints, error conditions, and critical differentiation from the 'rename_label' sibling tool that would be necessary for correct agent invocation.

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% with clear descriptions for 'oldName' and 'newName'. The description adds no additional semantic context about the parameters, but the schema is sufficient for understanding the inputs.

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

Purpose3/5

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

The description states the specific action (rename) and target resource (folder/category), but creates ambiguity by using 'folder/category' interchangeably without clarifying the relationship to the sibling 'rename_label' tool. It does not distinguish when to use this versus the label-specific variant.

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 provided on when to use this tool versus 'rename_label' or other folder manipulation tools like 'delete_folder'. No mention of prerequisites (e.g., whether the folder must exist) or constraints on naming.

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