Skip to main content
Glama
LarsCanGit

obs-mcp-server

by LarsCanGit
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

remove_profile

Delete OBS Studio profiles to manage your streaming setup. Specify a profile name to remove it from your configuration.

Instructions

Delete an OBS profile. Cannot remove the currently active profile.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profile_nameYesName of the profile to delete.

Implementation Reference

  • obs-mcp-server.js:603-606 (handler)
    The handler function that executes the "remove_profile" tool by calling the OBS "RemoveProfile" command.
    case "remove_profile": {
  await obs.call("RemoveProfile", { profileName: args.profile_name });
  return ok({ removed_profile: args.profile_name });
}
  • obs-mcp-server.js:347-360 (schema)
    The registration and input schema definition for the "remove_profile" tool.
    {
  name: "remove_profile",
  description: "Delete an OBS profile. Cannot remove the currently active profile.",
  inputSchema: {
    type: "object",
    properties: {
      profile_name: {
        type: "string",
        description: "Name of the profile to delete.",
      },
    },
    required: ["profile_name"],
  },
},

Tool Definition Quality

A4/5.0
Behavior3/5

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

No annotations provided, so description carries full disclosure burden. It usefully reveals the active-profile constraint (behavioral limitation), but omits other critical destructive-operation details: whether deletion is permanent, error behavior if constraint is violated, or impact on associated scene collections.

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?

Two sentences, zero waste. Purpose front-loaded in first sentence; constraint follows immediately. Appropriate density for a single-parameter destructive operation.

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?

Adequate for low complexity (1 param, flat schema, no output). The active-profile constraint captures the primary business logic gotcha. Missing output/error details but acceptable given simple domain and 100% schema coverage.

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 has 100% coverage (profile_name fully described). With schema doing the heavy lifting, baseline is 3. Description adds implicit validation rule (cannot be active profile) but doesn't add syntax/format details beyond schema.

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?

Clear specific verb ('Delete') + resource ('OBS profile') combination. Effectively distinguishes from siblings: vs create_profile (creates), vs set_profile (switches), vs list_profiles (reads). The scope is immediately obvious.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit critical constraint 'Cannot remove the currently active profile' which functions as a when-not-to-use guardrail. Lacks explicit mention of alternatives (e.g., 'use set_profile to switch first') or positive 'when to use' guidance, preventing a 5.

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