Skip to main content
Glama

rename_label

Change the name of a label in FreshRSS to update categorization and improve feed organization.

Instructions

Rename a label

Input Schema

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

Implementation Reference

  • The 'rename_label' tool is registered in the 'registerTagTools' function, where it defines its input schema and provides the handler implementation that calls 'client.tags.rename'.
    server.registerTool(
      'rename_label',
      {
        description: 'Rename a label',
        inputSchema: renameTagSchema,
      },
      wrapTool('rename_label', async (args: z.infer<typeof renameTagSchema>) => {
        await client.tags.rename(args.oldName, args.newName);
        return textResult(`Renamed label "${args.oldName}" to "${args.newName}".`);
      })
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Rename' implies a mutation, the description fails to specify what happens if oldName doesn't exist, whether the operation is atomic, if it affects articles currently tagged with the label, or any permission requirements.

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 description is extremely brief at only three words. While it wastes no words, it is arguably too minimal to provide necessary context for a mutation operation with no annotations. However, it meets the criteria of being appropriately sized for conciseness (not verbose).

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?

Given this is a mutation tool with no annotations and no output schema, the description is insufficient. It lacks differentiation from similar sibling tools, error handling context, and behavioral constraints needed for safe invocation, falling below minimum viable completeness for this complexity level.

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 both parameters (oldName and newName). The description 'Rename a label' adds no additional semantic context beyond what the schema already provides, warranting the baseline score for high-coverage schemas.

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

Purpose2/5

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

The description 'Rename a label' is tautological, merely restating the tool name 'rename_label'. It fails to distinguish this tool from its sibling 'rename_folder', which is critical given the parameter descriptions reference 'folder/label' and both tools exist on the same server.

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 alternatives (e.g., rename_folder), prerequisites (such as label existence), or error conditions. The description offers no 'when-to-use' or 'when-not-to-use' context.

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