Skip to main content
Glama

delete_task

Remove tasks permanently from FluentBoards project management by specifying board and task IDs with confirmation for safety.

Instructions

Delete a task permanently

Input Schema

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

Implementation Reference

  • The handler function that performs safety validation using validateDeleteOperation, calls the API to delete the task if allowed, and formats the response.
    async (args) => {
      const { board_id, task_id, confirm_delete } = args;
      
      // Validate delete operation safety
      const safetyCheck = validateDeleteOperation("task", confirm_delete);
      if (!safetyCheck.allowed) {
        return formatResponse(createDeleteSafetyError(safetyCheck));
      }
      
      const response = await api.delete(`/projects/${board_id}/tasks/${task_id}`);
      return formatResponse(response.data);
    }
  • Zod input schema defining required board_id and task_id, optional confirm_delete for safety.
    {
      board_id: z.number().int().positive().describe("Board ID"),
      task_id: z.number().int().positive().describe("Task ID"),
      confirm_delete: z.union([z.boolean(), z.string()]).optional().describe("Confirmation required: set to true, 'yes', or 'confirm' to proceed"),
    },
  • The server.tool call that registers the delete_task tool, including name, description, schema, and handler function.
    // Delete a task
    server.tool(
      "delete_task",
      "Delete a task permanently",
      {
        board_id: z.number().int().positive().describe("Board ID"),
        task_id: z.number().int().positive().describe("Task 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, task_id, confirm_delete } = args;
        
        // Validate delete operation safety
        const safetyCheck = validateDeleteOperation("task", confirm_delete);
        if (!safetyCheck.allowed) {
          return formatResponse(createDeleteSafetyError(safetyCheck));
        }
        
        const response = await api.delete(`/projects/${board_id}/tasks/${task_id}`);
        return formatResponse(response.data);
      }
    );
  • Helper function to validate delete operations based on configuration flags for enabled deletes, allowed types, and confirmation requirement.
    export function validateDeleteOperation(
      deleteType: DeleteType, 
      confirmDelete?: boolean | string
    ): DeleteSafetyResult {
      const { deleteSafety } = config;
    
      // Check if deletes are enabled at all
      if (!deleteSafety.enableDeletes) {
        return {
          allowed: false,
          reason: `Delete operations are disabled. Set ENABLE_DELETES=true in environment to enable.`,
          code: "DELETES_DISABLED"
        };
      }
    
      // Check if this specific delete type is allowed
      if (deleteSafety.allowedDeleteTypes.length > 0 && 
          !deleteSafety.allowedDeleteTypes.includes(deleteType)) {
        return {
          allowed: false,
          reason: `Delete operations for '${deleteType}' are not allowed. Allowed types: ${deleteSafety.allowedDeleteTypes.join(', ')}`,
          code: "DELETE_TYPE_NOT_ALLOWED"
        };
      }
    
      // Check confirmation requirement
      if (deleteSafety.requireConfirmation) {
        const confirmValue = typeof confirmDelete === "string" 
          ? confirmDelete.toLowerCase() 
          : confirmDelete;
        
        if (confirmValue !== true && confirmValue !== "yes" && confirmValue !== "confirm") {
          return {
            allowed: false,
            reason: `Confirmation required for delete operations. Add 'confirm_delete: true' or 'confirm_delete: "yes"' parameter.`,
            code: "CONFIRMATION_REQUIRED"
          };
        }
      }
    
      return { allowed: true };
    }
  • Helper function to create a standardized error response for failed delete safety checks.
    export function createDeleteSafetyError(result: DeleteSafetyError) {
      return {
        error: "Delete operation not allowed",
        reason: result.reason,
        code: result.code,
        message: "Delete operation blocked by safety configuration"
      };
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action is 'permanent', which is useful, but lacks critical details: it doesn't mention authentication requirements, rate limits, error conditions, or what happens to associated data (e.g., comments, labels). For a destructive operation, this is a significant gap.

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 waste. It's front-loaded with the core action and includes the key qualifier 'permanently' without unnecessary elaboration.

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 should address critical context like permissions needed, confirmation mechanisms (hinted by 'confirm_delete' parameter but not explained), and what the tool returns (success/failure indicators). The permanence warning is a start but insufficient.

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 three parameters. The description adds no additional parameter semantics beyond implying deletion requires board and task IDs, which is already clear from the schema. Baseline 3 is appropriate when 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 verb ('Delete') and resource ('a task') with the qualifier 'permanently', which distinguishes it from temporary removal operations. However, it doesn't explicitly differentiate from sibling tools like 'remove_label' or 'delete_label', which might have similar permanence implications.

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 'update_task' for archiving or 'change_task_status' for marking as done. It mentions 'permanently' but doesn't specify prerequisites or warn about irreversible consequences in relation to other tools.

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