Skip to main content
Glama
Sign In
OBS MCP

OBS MCP

by Tom-R-Main
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

Trigger Media Input Action

obs-trigger-media-input-action

Trigger play, pause, stop, restart, next, or previous actions on a specified media input in OBS Studio via natural language commands.

Instructions

Triggers an action on a media input

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "inputName": "<inputName>",
      "mediaAction": "<mediaAction>"
    },
    "name": "obs-trigger-media-input-action"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputNameYesName of the media input
mediaActionYesAction to trigger (PLAY, PAUSE, STOP, RESTART, NEXT, PREVIOUS)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations indicate no readOnly, so it mutates media input state, but the description doesn't add behavioral context like potential side effects (e.g., stopping playback) or irreversible actions. No output schema, so no return details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single, concise sentence, but under-specified for a tool with multiple actions. It is appropriately short, not verbose, but lacks useful detail the sentence could add.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that there is no output schema and limited annotations, the description should explain behavior or side effects but does not. The tool is straightforward but could benefit from clarifying that actions map directly to OBS media controls.

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 already describes both parameters with clear names and enums; description adds minimal value beyond restating the action enum. Since schema coverage is 100%, baseline is 3, but no additional format or context is provided.

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 clearly states it triggers an action on a media input, with specific verbs and resource. It distinguishes itself from media status/cursor tools but could be more specific about what actions entail.

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 guidance on when to use this tool versus alternatives, such as when to use pause/play vs stop/restart. The sibling tools include get-media-input-status, but no mention of checking status before actions or any prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools