Retrieve a list of all scene items in a specified OBS group by providing the group name or UUID. Use it to inspect group contents for scene management and automation.
Get a list of all scene items in a group
| Name | Required | Description | Default |
|---|---|---|---|
| sceneName | No | The name of the group to get items from | |
| sceneUuid | No | The UUID of the group to get items from |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. 'Get' implies a read, but it says nothing about permissions, behavior when no identifier is supplied, errors for nonexistent groups, return shape, or pagination.
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 definition is a single front-loaded sentence with no filler. Its brevity is efficient, though it also contributes to the missing invocation guidance.
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 read tool, the description still omits how to identify the group when both parameters are optional, whether the identifiers are mutually exclusive, and what the returned list contains. Without annotations or an output schema, those gaps are material.
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 already documents both parameters with 100% description coverage. The description adds no detail about precedence or exclusivity between sceneName and sceneUuid, so it stays at the baseline for high schema coverage.
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?
States a specific verb and resource: 'Get a list of all scene items in a group.' The 'in a group' qualifier distinguishes it from the sibling obs-get-scene-items, though the description does not explicitly name that alternative.
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?
Gives no when-to-use guidance, no alternatives, and no indication whether to supply sceneName, sceneUuid, or both. Since neither parameter is required, the description leaves the invocation choice unexplained.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.