Skip to main content
Glama
LarsCanGit

obs-mcp-server

by LarsCanGit
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

create_scene

Create a new empty scene in OBS Studio to organize your streaming or recording setup.

Instructions

Create a new empty scene in OBS.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scene_nameYesName for the new scene.

Implementation Reference

  • obs-mcp-server.js:539-542 (handler)
    The handler for 'create_scene' which calls the OBS 'CreateScene' method.
    case "create_scene": {
  await obs.call("CreateScene", { sceneName: args.scene_name });
  return ok({ created: args.scene_name });
}
  • obs-mcp-server.js:232-240 (registration)
    Tool registration for 'create_scene'.
    name: "create_scene",
description: "Create a new empty scene in OBS.",
inputSchema: {
  type: "object",
  properties: {
    scene_name: {
      type: "string",
      description: "Name for the new scene.",
    },

Tool Definition Quality

B3.2/5.0
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 adds 'empty' indicating the scene starts without sources, but omits mutation side effects, idempotency behavior (duplicate names), auth requirements, and return value structure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise at 7 words with zero redundancy. However, extreme brevity contributes to under-specification for a mutation tool; one additional sentence covering error cases or sibling distinction would improve utility without harming structure.

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 creation tool with complete schema coverage, but bare minimum. Missing: error behavior for duplicate names, confirmation of return value (void vs object), and relationship to 'set_scene' workflow.

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 parameter 'scene_name' fully described in the schema ('Name for the new scene'). The description provides no additional parameter semantics beyond the schema, warranting the baseline score of 3.

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?

The description uses specific verb 'Create' and resource 'scene', and specifies 'empty' and 'OBS' context. However, it does not explicitly distinguish from sibling tools like 'set_scene' (which activates existing scenes) or 'rename_scene'.

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 siblings like 'set_scene' or error handling if scene name already exists. No prerequisites or workflow context (e.g., 'create before switching') mentioned.

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