Skip to main content
Glama
Sign In
OBS MCP

OBS MCP

by Tom-R-Main
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

Remove Scene

obs-remove-scene
DestructiveIdempotent

Remove an existing scene from OBS by providing its name, optionally specifying a canvas UUID. Useful for cleaning up unused scenes in your current setup.

Instructions

Remove a scene from OBS

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sceneName": "<sceneName>"
    },
    "name": "obs-remove-scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
sceneNameYesThe name of the scene to remove
canvasUuidNoUUID of the canvas containing the scene

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.5/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description adds no extra behavioral context, such as what happens to scene items contained in the scene or whether the scene must not be currently active. The description merely restates the action without elaborating on side effects or requirements.

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?

The description is a single concise sentence that immediately conveys the purpose. It has no wasted words and is appropriately front-loaded.

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?

The tool is simple with good annotations covering destructiveness and idempotency, and parameters are fully described. However, the description does not mention the destructive side effects on contained scene items or any constraints (e.g., cannot remove an active scene), which would be useful context for a destructive operation. It is adequate but has gaps.

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%, so both sceneName and canvasUuid are documented. The description does not add any additional meaning beyond the schema's parameter descriptions, so the baseline 3 applies.

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 clearly states 'Remove a scene from OBS', using a specific verb 'remove' and resource 'scene'. It distinguishes from siblings like obs-create-scene and obs-set-scene-name, which handle other scene operations.

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?

The description implies the tool is for removing scenes, but it does not mention when to use it versus alternatives (e.g., obs-remove-scene-item for removing items within a scene) or any prerequisites like the scene needing to exist. No explicit when-not guidance is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools