atlas-mcp-server

by cyanheads
Verified

delete_task

Remove a task and all its children from the system.

When to Use:

  • Removing obsolete tasks
  • Cleaning up completed work
  • Restructuring project organization
  • Handling cancelled features

Best Practices:

  • Verify task is truly obsolete
  • Check for dependent tasks
  • Document deletion reasoning
  • Consider archiving instead
  • Handle child tasks appropriately

Example: { "path": "project/backend/deprecated-auth", "reasoning": "Removing deprecated authentication implementation as we've switched to OAuth2. All dependent tasks have been updated to reference the new OAuth2 implementation path." }

Input Schema

NameRequiredDescriptionDefault
pathYesPath of task to delete. Will also remove all child tasks. Note: This operation: - Removes the specified task - Removes all child tasks recursively - Updates dependencies in related tasks - Cannot be undone
reasoningNoExplanation for task deletion. Best practices: - Document why the task is no longer needed - Explain impact on dependent tasks - Note any replacement tasks - Record archival location if applicable

Input Schema (JSON Schema)

{ "properties": { "path": { "description": "Path of task to delete. Will also remove all child tasks.\nNote: This operation:\n- Removes the specified task\n- Removes all child tasks recursively\n- Updates dependencies in related tasks\n- Cannot be undone", "type": "string" }, "reasoning": { "description": "Explanation for task deletion. Best practices:\n- Document why the task is no longer needed\n- Explain impact on dependent tasks\n- Note any replacement tasks\n- Record archival location if applicable", "type": "string" } }, "required": [ "path" ], "type": "object" }