OBS MCP

Create scene collection

create_scene_collection

Creates a new OBS scene collection to organize scenes and sources for separate recording or streaming setups.

Instructions

Create a new OBS scene collection. Medium risk.

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": {
      "collection_name": "<collection_name>"
    },
    "name": "create_scene_collection"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	No
`collection_name`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 14, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations provided, the description must disclose behavioral details. It only adds 'Medium risk', which is vague and does not explain what the risk entails, whether the new collection becomes active, or if it requires OBS to be running. The behavior after creation is undisclosed, such as potential switching or overwriting.

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 very concise with two short statements. It front-loads the purpose and does not waste words, though 'Medium risk' is somewhat vague but still brief.

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?

The tool is a mutation (create) with no annotations and a minimal description. It lacks context about the effect on the current OBS session, whether the new collection is auto-selected, or how it relates to list_scene_collections. The output schema exists but the description does not indicate what to expect on success or error.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It does not mention the parameters 'collection_name' or 'confirm' at all. While the schema titles give hints, 'confirm' with default false is ambiguous, and the description adds no clarification.

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?

The description clearly states the action: 'Create a new OBS scene collection.' It uses the specific verb 'Create' and the resource 'OBS scene collection', which distinguishes it from sibling tools like create_scene or list_scene_collections.

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?

The description provides no usage guidance. It does not state when to use this tool versus alternatives like set_current_scene_collection or create_scene, nor mention prerequisites or exclusions. The only clue is the verb 'create', which implies the intended use but without explicit context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server