Skip to main content
Glama

remove_labels

Remove labels from articles in FreshRSS to organize your RSS feeds by deleting unwanted tags from specific posts.

Instructions

Remove labels from articles

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
articleIdsYesArticle IDs to modify
labelsYesLabel names to add/remove

Implementation Reference

  • The handler function for the 'remove_labels' tool, which takes articleIds and labels, and calls client.tags.removeFromArticles.
    wrapTool('remove_labels', async (args: z.infer<typeof modifyLabelsSchema>) => {
      await client.tags.removeFromArticles(args.articleIds, args.labels);
      return textResult(
        `Removed labels [${args.labels.join(', ')}] from ${args.articleIds.length.toString()} article(s).`
      );
    })
  • The registration of the 'remove_labels' tool on the server instance.
    server.registerTool(
      'remove_labels',
      {
        description: 'Remove labels from articles',
        inputSchema: modifyLabelsSchema,
      },
      wrapTool('remove_labels', async (args: z.infer<typeof modifyLabelsSchema>) => {
        await client.tags.removeFromArticles(args.articleIds, args.labels);
        return textResult(
          `Removed labels [${args.labels.join(', ')}] from ${args.articleIds.length.toString()} article(s).`
        );
      })
    );
  • The input schema 'modifyLabelsSchema' used by 'remove_labels'.
    export const modifyLabelsSchema = z
      .object({
        articleIds: z.array(z.string()).min(1).describe('Article IDs to modify'),
        labels: z.array(z.string()).min(1).describe('Label names to add/remove'),
      })
      .strict();
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It fails to indicate whether the operation is atomic (partial failure handling), idempotent (removing non-existent labels), or what constitutes success. No mention of side effects or permissions required.

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 concise at four words with zero redundancy. Every word earns its place. However, given the lack of annotations and output schema, the description could benefit from additional sentences without violating conciseness principles.

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?

As a mutation tool with no annotations and no output schema, the description is insufficient. It does not describe the return value, success indicators, or error scenarios. The agent must know what happens when invalid article IDs or non-existent labels are provided.

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?

With 100% schema description coverage, the schema already documents both parameters ('Article IDs to modify' and 'Label names to add/remove'). The description adds no additional semantic information about parameter formats, validation rules, or constraints beyond the schema.

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?

The description provides a clear verb (Remove), resource (labels), and scope (from articles). The phrase 'from articles' effectively distinguishes this tool from the sibling 'delete_label' tool, clarifying that labels are being unassigned rather than permanently deleted from the system.

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?

The description provides no guidance on when to use this tool versus alternatives like 'add_labels'. It does not mention prerequisites (e.g., that articles and labels must exist) or whether the operation is idempotent.

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