Skip to main content
Glama
Sign In
OBS MCP

OBS MCP

by Tom-R-Main
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

Set Current Profile

obs-set-current-profile
Idempotent

Switch OBS Studio to a specified profile by name, enabling quick changes to scene collections, settings, and hotkeys for different workflows.

Instructions

Switches to a profile

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": {
      "profileName": "<profileName>"
    },
    "name": "obs-set-current-profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileNameYesName of the profile to switch to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations document idempotentHint=true, destructiveHint=false, and readOnlyHint=false, which already convey the safety and mutation profile. The description adds no behavioral context beyond 'switches', such as side effects on other settings, so it contributes only minimal value beyond annotations.

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, short sentence that conveys the essential action with no wasted words. For a simple setter tool, this is appropriately sized and front-loaded.

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 tool's simplicity, one well-described parameter, and supportive annotations, the description is nearly complete. It lacks only minor context like 'switches the current/active profile' or 'profile must exist', but overall it is sufficient for an agent to understand the tool's purpose.

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% and the single profileName parameter is already described as 'Name of the profile to switch to'. The description adds no additional parameter-level meaning, so the baseline of 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 uses a specific verb ('Switches') and resource ('profile'), clearly indicating the action of changing the active profile. It is distinct from sibling tools like obs-create-profile, obs-remove-profile, and obs-get-profile-list, and the title reinforces 'Set Current Profile'.

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 is provided on when to use this tool versus alternatives such as obs-get-profile-list or obs-create-profile. The description states the action but gives no context about prerequisites, such as needing to list available profiles first or that the profile must already exist.

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