tasks_update

Update task statuses in bulk by ID using the MCP Tasks server. Automatically generates a summary, prevents accidental renaming or deletion, and ensures proper task organization without additional calls.

Instructions

Update tasks in bulk by ID to a different status. Returns complete summary no need to call tasks_summary afterwards. Prevents AI accidentally rename or deleting tasks during mass updates, not even possible

Input Schema

Name	Required	Description
`ids`	Yes	The IDs of existing tasks
`index`	No	0-based index to place the tasks. e.g.: - 0 for "Do this next" - Omit to place at the end ("Do this later")
`source_id`	No	Source ID from task_setup() response - Defaults to most recent in the workspace if not provided - Try to always provide it! - If you don't have it, ask the user for a file path and call task_setup()
`status`	Yes	You might need to infer it from the context: - "To Do" for tasks coming up next (e.g. "Do X next") - "In Progress" for what you'll do now (e.g. "First do X") - "Reminders" instructions for you (the AI) to be constantly reminded of - "Notes" to collect non-actionable notes - "Deleted" when they want these removed - Updating tasks to In Progress moves others to To Do, finishing a In Progress task moves the first Done to In Progress

Input Schema (JSON Schema)

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "additionalProperties": false,
  "properties": {
    "ids": {
      "description": "The IDs of existing tasks",
      "items": {
        "type": "string"
      },
      "type": "array"
    },
    "index": {
      "description": "0-based index to place the tasks. e.g.:\n- 0 for \"Do this next\"\n- Omit to place at the end (\"Do this later\")",
      "minimum": 0,
      "type": "integer"
    },
    "source_id": {
      "description": "Source ID from task_setup() response\n- Defaults to most recent in the workspace if not provided\n- Try to always provide it!\n- If you don't have it, ask the user for a file path and call task_setup()",
      "minLength": 1,
      "type": "string"
    },
    "status": {
      "anyOf": [
        {
          "description": "You might need to infer it from the context:\n- \"To Do\" for tasks coming up next (e.g. \"Do X next\")\n- \"In Progress\" for what you'll do now (e.g. \"First do X\")\n- \"Reminders\" instructions for you (the AI) to be constantly reminded of\n- \"Notes\" to collect non-actionable notes",
          "enum": [
            "In Progress",
            "To Do",
            "Backlog",
            "Done",
            "Reminders",
            "Notes",
            "Deleted"
          ],
          "type": "string"
        },
        {
          "const": "Deleted",
          "type": "string"
        }
      ],
      "description": "You might need to infer it from the context:\n- \"To Do\" for tasks coming up next (e.g. \"Do X next\")\n- \"In Progress\" for what you'll do now (e.g. \"First do X\")\n- \"Reminders\" instructions for you (the AI) to be constantly reminded of\n- \"Notes\" to collect non-actionable notes\n- \"Deleted\" when they want these removed\n- Updating tasks to In Progress moves others to To Do, finishing a In Progress task moves the first Done to In Progress"
    }
  },
  "required": [
    "ids",
    "status"
  ],
  "type": "object"
}

MCP Tasks

tasks_update

Instructions

Input Schema

Input Schema (JSON Schema)

Other Tools from MCP Tasks

Related Tools

MCP directory API