trigger_flowTrigger a Homey flow by its ID for immediate execution. Supports both simple and advanced flow types.
Trigger (run) a flow immediately by its ID. Tries simple flow first, then advanced flow. Use list_flows to find the flow ID.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Flow ID |
Changes observed during successful MCP inspections.
v2.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Adds behavioral detail beyond annotations: 'Tries simple flow first, then advanced flow' and 'immediately' describe execution order and immediacy. Annotations already cover read-only/destructive/idempotent hints, so this extra context enriches understanding without contradiction.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences with no filler. The purpose is front-loaded, followed by a useful behavioral note and a direct lookup instruction, making every sentence earn its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with a single parameter, no output schema, and existing annotations, the description fully covers purpose, prerequisite, and key behavior. Sibling context reinforces that this is the only flow-triggering tool, so no further details are necessary.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema describes 'id' as 'Flow ID' with 100% coverage, and the description reinforces it by stating 'by its ID' and pointing to list_flows for lookup. This adds practical guidance on how to obtain the value, going beyond the schema's minimal label.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description opens with 'Trigger (run) a flow immediately by its ID' – a specific verb and resource that clearly conveys the action. It distinguishes from sibling tools like list_flows and set_flow_enabled by focusing on execution rather than listing or toggling.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly instructs 'Use list_flows to find the flow ID,' providing prerequisite guidance for obtaining the required parameter. No alternative trigger tool exists among siblings, so context is clear, though it lacks an explicit 'when not to use' statement.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.