Retrieve private settings for a specific OBS scene item, using its scene and item ID, to inspect or debug item configuration.
Gets the private settings of a scene item
| Name | Required | Description | Default |
|---|---|---|---|
| sceneName | No | Name of the scene the item is in | |
| sceneUuid | No | UUID of the scene the item is in | |
| sceneItemId | Yes | Numeric ID of the scene item |
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. It implies a read-only operation via 'Gets,' but does not disclose permission requirements, whether private settings are sensitive, error behavior, or what the response 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 a single, front-loaded sentence with no wasted wording. For this simple getter, the concise phrasing is appropriate and readable.
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?
The tool is relatively simple, the input schema is fully documented, and there is no output schema. However, without annotations or return-value explanation, the description remains minimally adequate but does not fully explain what private settings are returned.
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?
Schema description coverage is 100%, so the input schema already documents sceneName, sceneUuid, and sceneItemId. The description adds no additional parameter meaning beyond what the schema provides, which is the baseline expectation for a fully documented schema.
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 states a specific verb and resource: getting the private settings of a scene item. It is clear what the tool does, but it does not explicitly distinguish itself from the sibling setter obs-set-scene-item-private-settings or the source-level variant obs-get-source-private-settings.
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?
There is no guidance on when to use this tool, when not to use it, or which sibling to choose for related operations. The read intent is implied by 'Gets,' but alternatives such as obs-set-scene-item-private-settings are not mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.