Skip to main content
Glama
Sign In
OBS MCP

OBS MCP

by Tom-R-Main
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

Create Scene Item

obs-create-scene-item

Add a source to an OBS scene as a scene item, specifying the scene and source by name or UUID. Set the item's initial visibility to control what appears in the composition.

Instructions

Create a scene item for a source in a scene

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "obs-create-scene-item"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledNoWhether the scene item is enabled/visible (default: true)
sceneNameNoName of the scene to add the source to
sceneUuidNoUUID of the scene to add the source to
canvasUuidNoUUID of the canvas containing the scene
sourceNameNoName of the source to add
sourceUuidNoUUID of the source to add

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already indicate readOnlyHint=false, so the mutation is known. The description adds no behavioral context such as duplicate behavior, error conditions, or what happens if identifiers are invalid, making it minimally informative beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no filler. It efficiently states the action and target resource.

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?

With six optional parameters and no output schema, the description should clarify identifier alternatives (sceneName vs sceneUuid, sourceName vs sourceUuid) and what the tool returns. It provides none of this context, making it incomplete for correct invocation.

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 six parameters are already documented in the input schema. The description adds no additional parameter semantics, so the baseline score of 3 is 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?

Description uses a specific verb ('Create') and clearly identifies the resource ('scene item') and context ('for a source in a scene'). This distinguishes it from sibling tools like obs-remove-scene-item and obs-duplicate-scene-item.

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, nor are prerequisites mentioned such as the source and scene needing to exist. The usage context is only implied by the tool name.

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