Skip to main content
Glama

delete_label

Remove a label from your FreshRSS feed reader to organize your RSS subscriptions and clean up your interface.

Instructions

Delete a label

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the folder/label to delete

Implementation Reference

  • The tool handler for 'delete_label', which takes a 'name' input and calls 'client.tags.delete(args.name)'.
    server.registerTool(
      'delete_label',
      {
        description: 'Delete a label',
        inputSchema: deleteTagSchema,
      },
      wrapTool('delete_label', async (args: z.infer<typeof deleteTagSchema>) => {
        await client.tags.delete(args.name);
        return textResult(`Deleted label "${args.name}".`);
      })
    );
  • The input schema definition for 'delete_label', requiring a 'name' field.
    export const deleteTagSchema = z
      .object({
        name: z.string().describe('Name of the folder/label to delete'),
      })
      .strict();
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 'Delete' implies destruction, the description doesn't specify what happens to articles tagged with this label, whether the operation is permanent, or if there are prerequisites.

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 a three-word fragment. While not verbose, it is under-substantive rather than efficiently concise—every sentence (here, fragment) does not earn its place given the ambiguity around folders vs. labels and delete vs. remove operations.

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 the complexity suggested by sibling tools (distinctions between labels and folders, deletion versus removal), the description is incomplete. It fails to clarify whether this deletes the label category entirely or removes it from articles, and doesn't address the folder/label relationship noted in the schema.

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% (the 'name' parameter is fully described in the schema as 'Name of the folder/label to delete'). The description adds no parameter semantics beyond the schema, warranting the baseline score of 3.

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 'Delete a label' is a tautology that restates the tool name. It fails to distinguish from siblings like 'remove_labels' (which likely removes labels from articles rather than deleting the label definition) and 'delete_folder' (given the schema mentions 'folder/label').

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 versus 'remove_labels' or 'delete_folder'. Given the schema description conflates 'folder/label', the description should clarify the specific use case but does not.

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