Retrieve saved playback scenes stored in the local sidecar. Use this to view your custom scenes and select one for playback.
List saved playback scenes from the local sidecar
| Name | Required | Description | Default |
|---|---|---|---|
| response_format | No | 'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API object | concise |
Changes observed during successful MCP inspections.
v1.26.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral burden. It usefully communicates that this is a read-only listing of locally stored sidecar data, but it doesn't specify behavior when the sidecar is missing, whether the listing is purely local, or what the returned list contains.
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?
The description is one short sentence with no filler. It front-loads the action and resource and every word contributes meaning.
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 low-complexity listing tool with one optional, well-documented parameter, the description is largely sufficient. The only minor gaps are that 'scenes' and 'local sidecar' are not defined in more detail and there is no output schema, but the phrase 'List saved playback scenes' conveys the expected result adequately.
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 input schema fully documents the single response_format parameter, including its enum values, default, and meaning, so the description adds nothing beyond the schema. Schema coverage is 100%, so the baseline 3 applies.
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?
The description uses the explicit verb 'List' and names the resource 'saved playback scenes' plus the source 'local sidecar', making the operation unambiguous. This clearly differentiates it from sibling tools such as save_scene, delete_scene, and apply_scene that operate on the same entity with different actions.
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?
No when-to-use or alternative guidance is provided. The description doesn't explain when to choose this over similar list-style siblings like list_playback_states, list_sessions, or list_backups, and it gives no prerequisites or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.