Skip to main content
Glama
Sign In
OBS MCP

OBS MCP

by Tom-R-Main
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

Set Scene Item Visibility

obs-set-scene-item-enabled
Idempotent

Shows or hides a scene item by its ID. Toggle visibility with a boolean to show or hide the item in a scene. Use this to control which items appear in your live composition.

Instructions

Show or hide a scene item

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sceneItemId": "<sceneItemId>",
      "enabled": "<enabled>"
    },
    "name": "obs-set-scene-item-enabled"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYesWhether to show (true) or hide (false) the item
sceneNameNoName of the scene containing the item
sceneUuidNoUUID of the scene containing the item
canvasUuidNoUUID of the canvas containing the scene
sceneItemIdYesThe ID of the scene item

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true. The description adds the semantics of 'show' vs 'hide' based on the boolean, which is helpful but minimal. It does not add context about side effects or behavior beyond what annotations cover, so this is adequate but not rich.

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 extremely concise (5 words) with no fluff. It is front-loaded and gets straight to the point. However, it might be too terse, lacking useful context, but for a simple setter tool, it is efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool complexity is low, but there are 5 parameters and no output schema. The description does not clarify which scene identifier is required, potential errors, or the return value (likely empty). It also doesn't mention that the operation is idempotent (though annotation covers that). Given the need to know how to specify the item, the description is incomplete for safe usage.

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 all parameters are self-explanatory. The description does not add any parameter-specific information beyond what the schema provides. However, it does imply the meaning of 'enabled' but doesn't clarify the optional nature of sceneName vs sceneUuid. Baseline 3 is appropriate given high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Show or hide a scene item' clearly states the action (show/hide) and the resource (scene item). It distinguishes the tool's purpose from siblings like obs-get-scene-item-enabled (which reads visibility) and obs-set-scene-item-transform (which sets transform). However, it does not explicitly mention that it applies to a specific scene item identified by ID, though that is implied.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives or any prerequisites. It does not mention that the scene item must exist or that sceneName/UUID is required (though schema shows them optional, but likely one is needed). No exclusions or alternative tool references are given.

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