Skip to main content
Glama

Delete a scene config

automations_delete_scene
DestructiveIdempotent

Delete a Home Assistant scene config by ID and reload scenes. Requires confirm=True; otherwise it returns a safety prompt and deletes nothing.

Instructions

Delete a scene config, then reload scenes.

Without confirm=True returns a safety prompt and touches nothing; with confirm=True deletes /api/config/scene/config/<id> and calls the scene.reload service.

Returns: dict {"deleted": sid, ...} merged with HA's delete response, or {"status": "not_found", "scene_id": sid} when no scene has that id. Errors: returns {"error": "confirmation_required", "message": ..., "action": ...} when confirm is not True. Limits: requires confirm=True; deletion is immediate and permanent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoMust be True to actually delete the scene. False (default) returns a safety prompt instead of deleting anything.
scene_idYesScene id to delete, bare (e.g. 'movie_night') or prefixed ('scene.movie_night').

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.25.1
    • addedInput schema / properties / confirm / description
      Added value: +"Must be True to actually delete the scene. False (default) returns a safety prompt instead of deleting anything."
    • addedInput schema / properties / scene_id / description
      Added value: +"Scene id to delete, bare (e.g. 'movie_night') or prefixed ('scene.movie_night')."
  2. Addedv0.18.1

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds substantial behavioral detail: the safety prompt when confirm is false, the exact endpoint touched, the scene.reload service call, possible not_found result, confirmation_required error, and that deletion is immediate and permanent. This is rich context beyond the structured 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 front-loaded with the core action and then organized into safety, returns, errors, and limits sections. It is longer than strictly necessary given the output schema exists, but each section is relevant and the structure aids quick scanning.

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 a destructive mutation tool with annotations, a fully covered input schema, and an output schema, the description still supplies the critical safety context an agent needs: confirm gating, immediate permanence, endpoint behavior, and error outcomes. Nothing essential for correct invocation appears missing.

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 description coverage is 100%, so the schema already documents both scene_id and confirm. The description reinforces the confirm requirement, but it does not add syntax or semantic detail beyond what the schema provides, making the baseline 3 appropriate.

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 states a specific verb and resource: delete a scene config, then reload scenes. It distinguishes itself from siblings such as automations_delete_automation and automations_delete_script by naming the scene config resource, and the confirm requirement further differentiates the operation.

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?

It clearly explains the two invocation modes: without confirm=True it returns a safety prompt and touches nothing; with confirm=True it deletes and reloads. It does not name alternative tools or explicitly say when not to use this tool beyond the confirmation guard, so it falls short of full when/when-not/alternatives guidance.

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