Skip to main content
Glama
LarsCanGit

obs-mcp-server

by LarsCanGit
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

create_profile

Create a new OBS Studio profile to organize scene collections, sources, and settings for different streaming or recording workflows.

Instructions

Create a new OBS profile.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profile_nameYesName for the new profile.

Implementation Reference

  • obs-mcp-server.js:598-601 (handler)
    The handler implementation for the create_profile tool, which calls the OBS CreateProfile method.
    case "create_profile": {
  await obs.call("CreateProfile", { profileName: args.profile_name });
  return ok({ created_profile: args.profile_name });
}
  • obs-mcp-server.js:334-342 (registration)
    The tool registration for create_profile, defining its schema and description.
    name: "create_profile",
description: "Create a new OBS profile.",
inputSchema: {
  type: "object",
  properties: {
    profile_name: {
      type: "string",
      description: "Name for the new profile.",
    },

Tool Definition Quality

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Create' implies a write operation, the description fails to disclose: whether creation automatically switches to the new profile, what happens if the name already exists (error vs overwrite), or what the return value indicates.

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 single sentence is front-loaded with the action ('Create') and contains no redundant words. Given the simplicity of the tool (one required string parameter), this length is appropriate and efficient.

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?

For a single-parameter creation tool with no output schema and no annotations, the description is minimally sufficient. However, gaps remain regarding side effects (auto-switching behavior) and collision handling that would comport with the complexity of profile management implied by the sibling tools.

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?

Input schema has 100% description coverage ('Name for the new profile'), so the schema fully documents the parameter. The description adds no additional semantic information about constraints, naming rules, or validation, which is acceptable given the baseline of 3 for high schema coverage.

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 provides a clear verb ('Create') and resource ('OBS profile') with scope ('new'). It implicitly distinguishes from sibling 'set_profile' through the 'create' vs 'set' verb distinction, though it doesn't explicitly clarify when to choose this over alternatives like renaming existing profiles.

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 explicit guidance provided on when to use this tool versus alternatives like 'set_profile' (which switches profiles) or error handling if the profile already exists. The agent must infer usage solely from the verb choice.

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