Skip to main content
Glama

list_scenes

Retrieve all available scenes in OBS Studio to manage and switch between different visual layouts for streaming or recording.

Instructions

List all scenes in OBS.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the 'list_scenes' tool which calls OBS WebSocket 'GetSceneList' and formats the output.
    case "list_scenes": {
      const { scenes, currentProgramSceneName } =
        await obs.call("GetSceneList");
      return ok({
        current_scene: currentProgramSceneName,
        scenes: scenes.map((s) => s.sceneName).reverse(), // OBS returns bottom-first
      });
    }
  • The registration of 'list_scenes' within the TOOLS array.
      name: "list_scenes",
      description: "List all scenes in OBS.",
      inputSchema: { type: "object", properties: {} },
    },
Behavior3/5

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

No annotations provided, so description carries full burden. 'List' implies read-only safety, but description omits return format, pagination, or OBS-specific scope (current scene collection vs all).

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 6-word sentence with zero waste. Purpose front-loaded immediately.

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

Completeness4/5

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

Adequate for 0-param complexity despite lacking output schema. Could briefly note relationship to set_scene or scene collections, but sufficient for tool selection.

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

Parameters4/5

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

Zero parameters per input schema with 100% coverage; baseline score applies as no parameter documentation is required.

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?

Clear specific verb 'List' + resource 'scenes' + context 'in OBS'. Distinct from siblings create_scene, remove_scene, rename_scene, and set_scene through verb choice.

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

Usage Guidelines3/5

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

Provides implied usage through read operation verb distinguishing from write siblings (create/remove/set), but lacks explicit when-to-use guidance or relationship to set_scene workflow.

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