Skip to main content
Glama
homeassistant-ai

Home Assistant MCP Server

Official

Manage Assist Pipeline

ha_manage_pipeline
Destructive

List, get, create, update, or set preferred Assist pipelines. Configure conversation, STT, TTS, and wake-word settings.

Instructions

Manage Home Assistant Assist pipelines.

Use action='list' to discover pipeline IDs, action='get' to inspect one pipeline, action='create' or action='update' to write pipeline settings, and action='set_preferred' to choose the preferred pipeline.

EXAMPLES:

  • List pipelines: ha_manage_pipeline(action="list")

  • Get one pipeline: ha_manage_pipeline(action="get", pipeline_id="preferred")

  • Create by cloning preferred: ha_manage_pipeline( action="create", name="Local Assist", conversation_engine="conversation.local_llm", )

  • Create by cloning a specific pipeline: ha_manage_pipeline( action="create", base_pipeline_id="preferred", name="Local Assist", conversation_engine="conversation.local_llm", )

  • Update conversation agent and clear TTS voice: ha_manage_pipeline( action="update", pipeline_id="preferred", conversation_engine="conversation.local_llm", tts_voice="", )

  • Set preferred: ha_manage_pipeline( action="set_preferred", pipeline_id="preferred", )

Empty string clears nullable STT/TTS/wake-word fields. Non-nullable fields such as name, language, conversation_language, and conversation_engine must be omitted or non-empty.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoPipeline display name. Required when action='create'.
actionYesPipeline operation: list, get, create, update, or set_preferred.
languageNoPipeline language, e.g. 'en'.
tts_voiceNoText-to-speech voice. Pass empty string to clear.
stt_engineNoSpeech-to-text engine. Pass empty string to clear.
tts_engineNoText-to-speech engine. Pass empty string to clear.
pipeline_idNoAssist pipeline ID. Required for get, update, and set_preferred.
stt_languageNoSpeech-to-text language. Pass empty string to clear.
tts_languageNoText-to-speech language. Pass empty string to clear.
wake_word_idNoWake-word ID. Pass empty string to clear.
make_preferredNoFor create/update only, also set the resulting pipeline as preferred with an extra websocket call. Ignored for other actions.
base_pipeline_idNoPipeline ID to clone when creating. Omit to clone the preferred pipeline. Ignored for non-create actions.
wake_word_entityNoWake-word entity ID. Pass empty string to clear.
conversation_engineNoConversation agent entity ID or engine ID. Required when action='create'.
prefer_local_intentsNoWhether Home Assistant local intents should be preferred before the conversation engine.
conversation_languageNoConversation language, usually '*'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Beyond the destructiveHint annotation, the description adds key behavioral details: that empty strings clear nullable fields, that make_preferred requires an extra websocket call, and it shows creation is based on cloning. This enriches the agent's understanding beyond the annotation flags.

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 a clear purpose statement, action list, and commented examples. It is not overly verbose given the tool's complexity (16 parameters), but it could be more concise without losing clarity.

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?

Given the high parameter count and existence of an output schema, the description covers the main use cases, including special behaviors like clearing fields and cloning. It does not repeat output schema details, which is appropriate.

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?

The input schema covers 100% of parameters with descriptions, so the baseline is 3. The description adds slight extra context (e.g., nullable field clearing) but does not significantly expand on the schema descriptions.

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 the tool manages Home Assistant Assist pipelines and lists five distinct actions (list, get, create, update, set_preferred). This specific verb+resource combination distinguishes it from sibling tools like ha_get_entity or ha_manage_addon.

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

Usage Guidelines3/5

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

The description provides examples for each action, showing how to use the tool in practice. However, it does not explicitly state when not to use this tool or compare it to alternatives among siblings, leaving the agent to infer the scope.

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