Skip to main content
Glama
Home Assistant MCP Server

Home Assistant MCP Server

Official

Remove Todo Item

ha_remove_todo_item
Destructive

Remove specific items or all completed entries from a Home Assistant todo list by entity ID, enabling cleanup of shopping or task lists.

Instructions

Remove items from a Home Assistant todo list.

Give item or remove_completed=True, not both. Removal is permanent; to mark an item done instead, use ha_set_todo_item() with status="completed". removed lists the items the call asked for that are gone afterwards; with remove_completed=True that includes a completed item another client removed meanwhile. With auto-backup on, each item is backed up before it is removed; warnings names a backup not taken because the item could not be read or the backup could not start, and with remove_completed=True an item gone afterwards that was not completed when the list was read, so was not backed up.

EXAMPLES:

  • ha_remove_todo_item("todo.shopping_list", "Buy milk")

  • ha_remove_todo_item("todo.shopping_list", ["Buy milk", "Bread"])

  • ha_remove_todo_item("todo.shopping_list", remove_completed=True)

If a Claude Desktop user gets a 4-minute timeout with no result on this call, read the target back before repeating it, and tell them to wait a few seconds before clicking the manual-approve button, as clicking it too quickly is known to cause hangs in Claude Desktop. This workaround is specific to Claude Desktop.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "entity_id": "<entity_id>"
    },
    "name": "ha_remove_todo_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemNoItem to remove, or a list of items - each the item UID (from ha_get_todo) or the exact item summary/name. A string that names no item but holds a JSON array of strings is that list.
entity_idYesTodo list entity ID (e.g., 'todo.shopping_list')
remove_completedNoRemove every completed item

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv9.1.0
    • addedInput schema / properties / item / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / item / default
      Added value: +null
    • changedInput schema / properties / item / description
      Previous value: -"Item to remove - can be the item UID (from ha_get_todo) or the exact item summary/name"New value: +"Item to remove, or a list of items - each the item UID (from ha_get_todo) or the exact item summary/name. A string that names no item but holds a JSON array of strings is that list."
    • removedInput schema / properties / item / type
      Removed value: -"string"
    • addedInput schema / properties / remove_completed
      Added value: +{
      +  "default": false,
      +  "description": "Remove every completed item",
      +  "type": "boolean"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "entity_id",
      -  "item"
      -]New value: +[
      +  "entity_id"
      +]
  2. Changed1 schema field changedv8.6.0
    • changedInput schema / properties / item / description
      Previous value: -"Item to remove - can be the item UID or the exact item summary/name"New value: +"Item to remove - can be the item UID (from ha_get_todo) or the exact item summary/name"
  3. First observedv7.14.2

TDQS

A4.2/5.0
Behavior3/5

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

Goes well beyond the annotations (destructiveHint=true only signals risk) by stating removal is permanent, describing the auto-backup-before-removal behavior, and defining what `warnings` means. However, the sentence explaining `warnings` is tangled and hard to parse on first read, and the Claude Desktop timeout paragraph is a tooling workaround rather than a disclosure of this tool's behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core rule and the alternative are front-loaded, which is good, but the backup/`warnings` sentence is a dense multi-clause run-on, and the trailing Claude Desktop paragraph is long relative to its value. The examples are well-chosen and earn their space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers a destructive three-parameter tool thoroughly: permanence, backup, mutual exclusion, alternative, and even expected output fields, so an output schema is not strictly needed for return semantics. Only failure modes (entity not found, item name matching nothing) are left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds a genuine cross-parameter constraint absent from the schema: `item` and `remove_completed` are mutually exclusive. It also clarifies that strings may be a UID or an exact name, which the schema's anyOf does not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource ("Remove items from a Home Assistant todo list") and immediately contrasts itself with the sibling ha_set_todo_item() for the mark-done case. An agent can distinguish removal from completion without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States the selection constraint explicitly ("Give `item` or `remove_completed=True`, not both") and names the alternative tool with the exact argument needed (ha_set_todo_item with status="completed"). Both the when and the when-not are covered.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools