Skip to main content
Glama

delete_label

Remove a label permanently from a FluentBoards project board. This tool deletes labels to clean up board organization and requires confirmation to proceed with deletion.

Instructions

Delete a label from a board permanently

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
board_idYesBoard ID
label_idYesLabel ID
confirm_deleteNoConfirmation required: set to true, 'yes', or 'confirm' to proceed

Implementation Reference

  • Handler function that destructures arguments, performs safety validation for deletion, and executes the API DELETE request to remove the label from the board.
    async (args) => {
      const { board_id, label_id, confirm_delete } = args;
      
      // Validate delete operation safety
      const safetyCheck = validateDeleteOperation("label", confirm_delete);
      if (!safetyCheck.allowed) {
        return formatResponse(createDeleteSafetyError(safetyCheck));
      }
      
      const response = await api.delete(`/projects/${board_id}/labels/${label_id}`);
      return formatResponse(response.data);
    }
  • Zod schema defining input parameters for the delete_label tool: board_id, label_id, and optional confirm_delete.
    {
      board_id: z.number().int().positive().describe("Board ID"),
      label_id: z.number().int().positive().describe("Label ID"),
      confirm_delete: z.union([z.boolean(), z.string()]).optional().describe("Confirmation required: set to true, 'yes', or 'confirm' to proceed"),
    },
  • MCP server tool registration for 'delete_label', including name, description, input schema, and handler function.
      "delete_label",
      "Delete a label from a board permanently",
      {
        board_id: z.number().int().positive().describe("Board ID"),
        label_id: z.number().int().positive().describe("Label ID"),
        confirm_delete: z.union([z.boolean(), z.string()]).optional().describe("Confirmation required: set to true, 'yes', or 'confirm' to proceed"),
      },
      async (args) => {
        const { board_id, label_id, confirm_delete } = args;
        
        // Validate delete operation safety
        const safetyCheck = validateDeleteOperation("label", confirm_delete);
        if (!safetyCheck.allowed) {
          return formatResponse(createDeleteSafetyError(safetyCheck));
        }
        
        const response = await api.delete(`/projects/${board_id}/labels/${label_id}`);
        return formatResponse(response.data);
      }
    );
Behavior2/5

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

With no annotations, the description carries full burden. It discloses the permanent nature of deletion, which is critical behavioral context. However, it lacks details on permissions required, side effects (e.g., impact on tasks using the label), error handling, or confirmation mechanics beyond the parameter hint.

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, direct sentence with zero waste. It's front-loaded with the core action and key detail (permanence), making it highly efficient and easy to parse.

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 destructive tool with no annotations and no output schema, the description is incomplete. It mentions permanence but omits critical context like required permissions, irreversible consequences, error scenarios, or what happens to associated data. This leaves significant gaps for safe agent operation.

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%, so the schema already documents all parameters. The description adds no additional meaning about parameters beyond implying deletion requires board and label IDs, which is obvious from the schema. Baseline 3 is appropriate as 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 ('Delete') and target ('a label from a board'), and specifies it's permanent. However, it doesn't differentiate from sibling 'remove_label' which suggests a similar function, leaving some ambiguity about when to choose one over the other.

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 is provided on when to use this tool versus alternatives like 'remove_label' or 'edit_label'. The description mentions permanence but doesn't explain prerequisites, recovery options, or contextual triggers for deletion.

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