Skip to main content
Glama
LarsCanGit

obs-mcp-server

by LarsCanGit
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

list_profiles

Retrieve all OBS Studio profiles and identify the currently active one for managing broadcast configurations.

Instructions

List all OBS profiles and show which one is active.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • obs-mcp-server.js:582-589 (handler)
    The handler for "list_profiles" calls the OBS "GetProfileList" command and returns the current profile and the list of available profiles.
    case "list_profiles": {
  const { profiles, currentProfileName } =
    await obs.call("GetProfileList");
  return ok({
    current_profile: currentProfileName,
    profiles,
  });
}
  • obs-mcp-server.js:314-318 (registration)
    The tool registration for "list_profiles" including its description and input schema.
    {
  name: "list_profiles",
  description: "List all OBS profiles and show which one is active.",
  inputSchema: { type: "object", properties: {} },
},

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 adds valuable behavioral context by specifying the tool reveals active/inactive status, but omits other behavioral traits like error conditions, caching behavior, or response structure.

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?

Single 11-word sentence with zero redundancy. Immediately establishes resource (profiles), action (list), and key differentiator (active status) with optimal front-loading.

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?

Appropriately complete for a zero-parameter read operation. The mention of 'active' status covers the essential behavioral output despite absence of output schema.

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

Parameters4/5

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

Zero parameters present in schema, which per guidelines establishes a baseline score of 4. Description appropriately requires no parameter explanation.

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?

Description uses specific verb 'List' with resource 'OBS profiles' and adds distinguishing scope 'show which one is active,' clearly differentiating from sibling mutation tools (set_profile, create_profile, remove_profile).

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?

No explicit when-to-use or alternative recommendations provided. Usage is only implied by the read-only verb 'List' contrasting with siblings using action verbs (set, create, remove).

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