OBS MCP

Switch profile

set_current_profile

Switch OBS to a specified profile by providing its name. Use to change active profile settings for scenes, outputs, and more.

Instructions

Switch to another OBS profile. Medium risk.

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": {
      "profile_name": "<profile_name>"
    },
    "name": "set_current_profile"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	No
`profile_name`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 14, 2026

TDQS

B3/5.0

Behavior2/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 mentions 'Medium risk' but does not explain what the risk entails, whether confirmation is required, or what happens to the current profile. This leaves significant behavioral ambiguity for a mutating operation.

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 extremely concise at two short sentences with no filler. It front-loads the action and adds a brief risk note.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite its simplicity, the tool has a confirm parameter and a risk warning that are not elaborated. The output schema exists, so return values need not be explained, but the description fails to specify the behavior of confirmation and the nature of the risk, leaving the agent under-informed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It clarifies that profile_name is the target profile name, but the confirm parameter is never mentioned. The description adds minimal meaning beyond the schema's titles and types.

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 clearly states the action: switching to another OBS profile, using a specific verb and resource. It distinguishes from sibling tools like list_profiles and create_profile, though it does not explicitly contrast with alternatives.

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 use case (switching the active profile) but provides no explicit guidance on when to use this tool versus list_profiles or create_profile. No prerequisites or exclusions are mentioned.

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

Deploy Server