Skip to main content
Glama
LarsCanGit

obs-mcp-server

by LarsCanGit
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

set_scene_collection

Switch OBS Studio scene collections to reload scenes and change production setups. Specify the exact collection name to transition between different scene configurations.

Instructions

Switch to a different scene collection. OBS will reload its scenes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collection_nameYesExact name of the scene collection to switch to.

Implementation Reference

  • obs-mcp-server.js:567-572 (handler)
    Handler function for the set_scene_collection tool which calls the OBS WebSocket 'SetCurrentSceneCollection' method.
    case "set_scene_collection": {
  await obs.call("SetCurrentSceneCollection", {
    sceneCollectionName: args.collection_name,
  });
  return ok({ switched_to_collection: args.collection_name });
}
  • obs-mcp-server.js:284-296 (schema)
    Input schema definition for the set_scene_collection tool.
    {
  name: "set_scene_collection",
  description: "Switch to a different scene collection. OBS will reload its scenes.",
  inputSchema: {
    type: "object",
    properties: {
      collection_name: {
        type: "string",
        description: "Exact name of the scene collection to switch to.",
      },
    },
    required: ["collection_name"],
  },

Tool Definition Quality

B3.3/5.0
Behavior3/5

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

Annotations are absent, so description carries full burden. Adds valuable behavioral context with 'OBS will reload its scenes,' indicating a disruptive refresh operation. However, lacks critical safety details like whether unsaved changes are discarded, if the operation is atomic, or required permissions.

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?

Two efficient sentences with zero redundancy. Action and side effect are front-loaded; no filler words. Appropriate density for the tool's simplicity.

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

Completeness3/5

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

Adequate for a single-parameter state-change tool, covering the core operation and reload side effect. However, missing error handling behavior (e.g., invalid collection names) and return value description expected for a tool with no output schema and no annotations to provide safety hints.

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 coverage is 100% with the 'collection_name' parameter fully documented. Description contributes minimal additional semantics beyond the schema, though 'different' implies a state change. Baseline 3 appropriate when schema does heavy lifting.

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?

Clear verb 'Switch' and resource 'scene collection' identify the operation precisely. Uses specific OBS terminology that implicitly distinguishes from sibling 'set_scene' (which handles individual scenes) and 'set_profile' (which handles OBS profiles), though lacks explicit contrast.

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?

Provides no guidance on when to use this versus sibling tools like 'set_scene' or prerequisites such as whether streaming/recording must be stopped first. No mention of error conditions or valid states for invocation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/LarsCanGit/OBS-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server