Skip to main content
Glama
homeassistant-ai

Home Assistant MCP Server

Official

Set Todo Item

ha_set_todo_item
Destructive

Create or update a todo item in Home Assistant. Add new items with summary and optional details, or modify existing items by updating status, name, or due date.

Instructions

Create or update a todo item in Home Assistant.

WITHOUT item parameter (create mode): Creates a new item. summary is required.

WITH item parameter (update mode): Updates an existing item identified by UID or exact name. At least one update field (rename, status, description, due_date, due_datetime) is required.

EXAMPLES:

  • Add item: ha_set_todo_item("todo.shopping_list", summary="Buy milk")

  • Add with description: ha_set_todo_item("todo.shopping_list", summary="Buy milk", description="2% organic")

  • Add with due date: ha_set_todo_item("todo.tasks", summary="Pay bills", due_date="2024-12-31")

  • Complete item: ha_set_todo_item("todo.shopping_list", item="Buy milk", status="completed")

  • Rename item: ha_set_todo_item("todo.tasks", item="Old task", rename="New task name")

  • Update due date: ha_set_todo_item("todo.tasks", item="Pay bills", due_date="2024-12-31")

  • Reopen item: ha_set_todo_item("todo.tasks", item="Task to redo", status="needs_action")

NOTE: Not all todo integrations support all features (description, due dates). The Shopping List integration only supports summary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemNoExisting item to update - can be the item UID or the exact item summary/name. When provided, operates in update mode. When omitted, creates a new item.
renameNoNew name/summary for an existing item. Only used in update mode.
statusNoItem status: 'completed' to mark done, 'needs_action' to mark incomplete. Only used in update mode.
summaryNoItem text/name. Required when creating a new item. Ignored in update mode — use 'rename' to change the item name.
due_dateNoDue date in YYYY-MM-DD format (e.g., '2024-12-25')
entity_idYesTodo list entity ID (e.g., 'todo.shopping_list')
descriptionNoDetailed description for the item
due_datetimeNoDue datetime in ISO format (e.g., '2024-12-25T14:00:00'). Overrides due_date if both provided.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

Annotations include destructiveHint: true, confirming mutation. The description adds details about create/update modes and parameter behaviors but does not disclose potential side effects, permissions required, or reversibility. It provides adequate context beyond annotations.

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

Conciseness4/5

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

The description is well-structured with clear sections (create mode, update mode, examples, note) and front-loads the main action. While somewhat lengthy due to multiple examples, every sentence adds value and the structure aids readability.

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

Completeness5/5

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

Given the tool's complexity (8 params, two modes), the description covers all key aspects: mode behavior, required/optional params, integration limitations, and examples. With full schema coverage and an output schema present, no return value explanation is needed.

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%, but the description adds significant value by explaining param relationships (summary vs rename, due_datetime override), mode-switching via 'item', and providing concrete examples that clarify parameter usage beyond the schema definitions.

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?

The description clearly states 'Create or update a todo item in Home Assistant' and distinguishes two modes (create vs update) based on the 'item' parameter, which differentiates it from sibling tools like ha_remove_todo_item and ha_get_todo.

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

Usage Guidelines4/5

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

The description explicitly explains when to use create mode (no item) vs update mode (with item), provides detailed examples for each scenario, and notes limitations across integrations. However, it does not explicitly state when to avoid this tool (e.g., for deletion or listing).

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/homeassistant-ai/ha-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server