Skip to main content
Glama

remove_label

Remove a label from a task in FluentBoards project management to organize and categorize tasks effectively.

Instructions

Remove a label from a task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
board_idYesBoard ID
task_idYesTask ID
label_idYesLabel ID

Implementation Reference

  • Registers the 'remove_label' MCP tool, including input schema validation and the handler function that removes a label from a task by making a DELETE API request to the specified endpoint.
    server.tool(
      "remove_label",
      "Remove a label from a task",
      {
        board_id: z.number().int().positive().describe("Board ID"),
        task_id: z.number().int().positive().describe("Task ID"),
        label_id: z.number().int().positive().describe("Label ID"),
      },
      async (args) => {
        const { board_id, task_id, label_id } = args;
    
        const response = await api.delete(
          `/projects/${board_id}/tasks/${task_id}/labels/${label_id}`
        );
        return formatResponse(response.data);
      }
    );
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. It states the action ('Remove') but doesn't clarify if this is a destructive mutation, what permissions are required, whether changes are reversible, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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?

The description is a single, efficient sentence with zero wasted words. It front-loads the core action ('Remove a label from a task') without unnecessary elaboration. Every word earns its place, making it highly concise and well-structured.

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 incomplete. It doesn't address behavioral aspects like side effects, error conditions, or return values. While the schema covers parameters well, the overall context for safe and effective use is lacking, especially compared to siblings that may have similar gaps.

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 all three parameters clearly documented in the schema (board_id, task_id, label_id). The description adds no additional meaning beyond implying that a label is removed from a task, which the schema already covers through parameter names and descriptions. Baseline 3 is appropriate when the schema does the heavy lifting.

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 clearly states the action ('Remove') and the target ('a label from a task'), which is specific and unambiguous. It distinguishes itself from siblings like 'add_label' and 'delete_label' by focusing on removal from a task rather than creation or deletion of the label itself. However, it doesn't explicitly mention the board context that the parameters require, which slightly limits differentiation.

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. It doesn't mention prerequisites (e.g., needing an existing label on a task), exclusions (e.g., not for removing labels from boards directly), or comparisons to siblings like 'edit_label' or 'delete_label'. The agent must infer usage solely from the name and parameters.

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/danieliser/fluent-boards-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server