Skip to main content
Glama

set_scene

Switch OBS Studio to a different scene by specifying the exact scene name, enabling control of your streaming or recording setup.

Instructions

Switch OBS to a different scene.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scene_nameYesExact name of the scene to switch to.

Implementation Reference

  • The 'set_scene' handler implementation, which calls OBSWebSocket's 'SetCurrentProgramScene'.
    case "set_scene": {
      await obs.call("SetCurrentProgramScene", {
        sceneName: args.scene_name,
      });
      return ok({ switched_to: args.scene_name });
    }
  • The 'set_scene' tool definition and schema definition.
    {
      name: "set_scene",
      description: "Switch OBS to a different scene.",
      inputSchema: {
        type: "object",
        properties: {
          scene_name: {
            type: "string",
            description: "Exact name of the scene to switch to.",
          },
        },
        required: ["scene_name"],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but lacks behavioral details. It doesn't disclose whether the switch is immediate or deferred, what happens if OBS is not running, or how it affects ongoing recordings/streams.

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?

Single sentence of five words with zero redundancy. Front-loaded with action verb and scope (OBS), earning its place efficiently.

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?

Minimally viable for a single-parameter tool with full schema coverage, but gaps remain given lack of annotations and output schema. Could benefit from context about error conditions or state persistence.

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 has 100% description coverage for the single parameter ('Exact name of the scene to switch to'). Description adds no additional param semantics, but baseline 3 applies when schema coverage is complete.

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?

Specific verb 'Switch' + resource 'scene' clearly identifies the action. Distinguishes from siblings like 'create_scene', 'remove_scene', and 'list_scenes' which handle CRUD operations rather than activation.

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 provided on when to use this versus 'set_scene_collection' (which changes the entire scene collection) or how it interacts with active streaming/recording. No mention of prerequisites like requiring the scene to exist.

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