Skip to main content
Glama
LarsCanGit

obs-mcp-server

by LarsCanGit
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

remove_scene

Delete scenes from OBS Studio to manage your streaming or recording setup. Specify the scene name to remove it, but note that currently active scenes cannot be deleted.

Instructions

Delete a scene from OBS. Cannot remove the currently active scene.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scene_nameYesName of the scene to delete.

Implementation Reference

  • obs-mcp-server.js:544-547 (handler)
    The handler logic for the 'remove_scene' tool, which calls the OBS 'RemoveScene' command.
    case "remove_scene": {
  await obs.call("RemoveScene", { sceneName: args.scene_name });
  return ok({ removed: args.scene_name });
}
  • obs-mcp-server.js:246-255 (registration)
    The registration of the 'remove_scene' tool within the MCP server.
    name: "remove_scene",
description: "Delete a scene from OBS. Cannot remove the currently active scene.",
inputSchema: {
  type: "object",
  properties: {
    scene_name: {
      type: "string",
      description: "Name of the scene to delete.",
    },
  },

Tool Definition Quality

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the critical behavioral constraint regarding active scenes and implies destructiveness via 'Delete', but lacks other behavioral details like error modes, side effects on contained sources, or reversibility.

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 with two efficient sentences. The first states the action, the second states the critical constraint. No filler or redundant information.

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?

Given the simple single-parameter operation and lack of output schema, the description is appropriately complete. It covers the essential functional constraint. Could be improved by mentioning error behavior if the scene doesn't exist, but adequate for the complexity level.

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 description coverage is 100% ('Name of the scene to delete'), establishing baseline 3. The description implies the parameter's purpose by stating the action but does not add semantic details beyond what the schema already provides.

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?

The description states a specific verb ('Delete'), resource ('scene'), and context ('OBS'). It effectively distinguishes from sibling tools like 'set_scene' or 'rename_scene' by including the unique constraint about the currently active scene.

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

Usage Guidelines4/5

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

Provides a clear when-not constraint ('Cannot remove the currently active scene'), which guides the agent away from error conditions. However, it does not explicitly name the alternative workflow (e.g., 'use set_scene first to switch away').

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