Home Assistant MCP Server

Overview Schema Source Related Servers Discussions Admin

List automations

list_automations

Read-onlyIdempotent

Retrieve Home Assistant automations with their state, last triggered time, mode, and config ID. Filter by name or ID to locate automations for inspection or updates.

Instructions

List automations with their state, last triggered time, mode and config id. The id is what get_automation and save_automation take. Optionally filter by a word in the name or id.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_automations"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum rows.
`query`	No	Substring to match against name, entity id or config id.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Nov 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds value beyond that by disclosing what each row contains (state, last triggered time, mode, config id), which the annotations do not. It does not mention result volume or default paging behavior, keeping it short of a 5.

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?

Three short sentences, front-loaded with the core purpose and return contents, then the identifier relationship, then the optional filter. No redundant or filler wording.

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?

There is no output schema, so the description correctly carries the burden of naming the returned fields, and it does so. Combined with annotations covering the read-only nature and a fully described schema, an agent has what it needs; only paging expectations (default 100, max 300) are left to the schema alone.

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 coverage is 100%, so both parameters are already documented, setting the baseline at 3. The description restates the query behavior ("filter by a word in the name or id") in slightly narrower terms than the schema's "name, entity id or config id," and says nothing extra about the limit parameter.

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?

States the specific verb and resource ("List automations") and enumerates the returned fields (state, last triggered time, mode, config id). It also distinguishes itself from get_automation by explaining that this tool surfaces the id those tools consume.

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 sentence "The id is what get_automation and save_automation take" gives an explicit routing cue: list here first, then drill in with get_automation. It also notes the filter is optional. It lacks an explicit when-not-to-use statement (e.g., use search_entities for broader matching).

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