Skip to main content
Glama
LarsCanGit

obs-mcp-server

by LarsCanGit
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

start_recording

Begin recording video and audio in OBS Studio to capture live content or create video files.

Instructions

Start OBS recording.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • obs-mcp-server.js:400-403 (handler)
    Handler implementation for the 'start_recording' tool, which calls the OBS 'StartRecord' command.
    case "start_recording": {
  await obs.call("StartRecord");
  return ok({ recording: true });
}
  • obs-mcp-server.js:78-82 (registration)
    Tool registration for 'start_recording'.
    {
  name: "start_recording",
  description: "Start OBS recording.",
  inputSchema: { type: "object", properties: {} },
},

Tool Definition Quality

B3/5.0
Behavior2/5

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

No annotations provided, yet description fails to disclose idempotency rules (does it error if already recording?), file output location/format, or side effects. 'Start' implies state mutation but lacks behavioral specifics.

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?

Three words with zero redundancy. Appropriately sized for a no-parameter action command; every word 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?

Minimally sufficient for a simple command with no parameters or output schema, but lacks critical details about error conditions and interaction with stop_recording/toggle_recording siblings.

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; per guidelines this establishes a baseline of 4. Description appropriately reflects the empty parameter schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States specific verb (Start) and resource (OBS recording), but fails to distinguish from sibling tool toggle_recording. Doesn't clarify behavior when recording is already active.

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?

Provides no guidance on when to use this tool versus toggle_recording or start_streaming. No mention of prerequisites like active OBS connection or scene setup.

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