Skip to main content
Glama

create_scene_collection

Create a new scene collection in OBS Studio to organize and manage different sets of scenes for various streaming or recording scenarios.

Instructions

Create a new scene collection (starts empty).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collection_nameYesName for the new scene collection.

Implementation Reference

  • Handler implementation for "create_scene_collection" tool. It calls the OBS "CreateSceneCollection" command with the provided collection name.
    case "create_scene_collection": {
      await obs.call("CreateSceneCollection", {
        sceneCollectionName: args.collection_name,
      });
      return ok({ created_collection: args.collection_name });
    }
  • Schema registration for "create_scene_collection" tool, defining the input parameter `collection_name`.
    {
      name: "create_scene_collection",
      description: "Create a new scene collection (starts empty).",
      inputSchema: {
        type: "object",
        properties: {
          collection_name: {
            type: "string",
            description: "Name for the new scene collection.",
          },
        },
        required: ["collection_name"],
      },
Behavior3/5

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

With no annotations provided, the description carries full disclosure burden. It successfully communicates the initial empty state, but omits other behavioral traits: whether the collection becomes active automatically, what is returned, error conditions (e.g., duplicate names), or persistence guarantees. Adequate but incomplete.

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?

Extremely concise single sentence with verb-first structure. Every word earns its place: 'Create' establishes operation, 'new scene collection' identifies resource, '(starts empty)' provides essential behavioral context without verbosity.

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?

Appropriate for low-complexity tool with single well-documented parameter and no output schema. Covers core creation functionality but gaps remain regarding side effects (auto-switching behavior) and success/failure indicators. Sufficient but not comprehensive.

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 'collection_name' fully described in the schema. Description does not add parameter-specific semantics (e.g., naming constraints, uniqueness requirements, max length). Baseline score appropriate given schema completeness.

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 specific verb 'Create' and resource 'scene collection'. The parenthetical '(starts empty)' adds valuable specificity about initial state. Implicitly distinguishes from sibling 'create_scene' by specifying 'collection' and from 'set_scene_collection' by using 'Create' versus 'set', though explicit distinction would strengthen further.

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 explicit when-to-use guidance or comparison to alternatives like 'set_scene_collection'. The 'starts empty' phrase implies post-creation requirements but does not state prerequisites (e.g., name uniqueness) or clarify whether this automatically switches to the new collection versus merely creating it.

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