Skip to main content
Glama
LarsCanGit

obs-mcp-server

by LarsCanGit
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

set_profile

Switch OBS Studio profiles to change stream settings and encoder configurations using the obs-mcp-server.

Instructions

Switch to a different OBS profile (stream settings, encoder config, etc.).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profile_nameYesExact name of the profile to switch to.

Implementation Reference

  • obs-mcp-server.js:591-596 (handler)
    The handler logic for the "set_profile" tool which calls the OBS "SetCurrentProfile" method.
    case "set_profile": {
  await obs.call("SetCurrentProfile", {
    profileName: args.profile_name,
  });
  return ok({ switched_to_profile: args.profile_name });
}
  • obs-mcp-server.js:320-331 (schema)
    The registration and input schema definition for the "set_profile" tool.
    name: "set_profile",
description: "Switch to a different OBS profile (stream settings, encoder config, etc.).",
inputSchema: {
  type: "object",
  properties: {
    profile_name: {
      type: "string",
      description: "Exact name of the profile to switch to.",
    },
  },
  required: ["profile_name"],
},

Tool Definition Quality

A3.7/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses what configuration domains get affected (stream settings, encoder config), but omits operational details like whether this interrupts active streams, requires specific OBS states, or confirmation behavior.

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?

Ultra-concise at 11 words. The single sentence is front-loaded with the action verb, and the parenthetical efficiently adds scope context without waste. Every element earns its place.

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 switching tool with no output schema. The description covers the functional purpose, but given the lack of annotations and the potentially disruptive nature of switching encoder configs mid-stream, it lacks behavioral completeness regarding side effects or safety.

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%, so the baseline is 3. The description implies the 'profile_name' parameter by mentioning 'a different OBS profile' but does not add syntax, format constraints, or usage 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 uses a specific verb ('Switch') and resource ('OBS profile'), and the parenthetical clarifies what profiles contain ('stream settings, encoder config, etc.'), clearly distinguishing this from sibling scene/source operations like set_scene or set_source_visibility.

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 verb 'Switch' and the profile-specific context implicitly guide usage, but there is no explicit guidance on when to use this versus create_profile or list_profiles, nor any prerequisites mentioned (e.g., whether the profile must exist).

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