Skip to main content
Glama
Sign In
OBS MCP

OBS MCP

by Tom-R-Main
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

Set Source Filter Enabled

obs-set-source-filter-enabled
Idempotent

Enable or disable a filter on a specific source in OBS Studio by providing the source name, filter name, and desired enabled state.

Instructions

Sets the enable state of a source filter

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": {
      "sourceName": "<sourceName>",
      "filterName": "<filterName>",
      "filterEnabled": "<filterEnabled>"
    },
    "name": "obs-set-source-filter-enabled"
  }
}

Input Schema

NameRequiredDescriptionDefault
canvasUuidNoUUID of the canvas containing the source
filterNameYesName of the filter
sourceNameYesName of the source the filter is on
filterEnabledYesNew enable state of the filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the description is not required to restate these. It adds no further behavioral context beyond the action itself, such as immediate rendering effects or dependencies on source state. With annotations covering the safety profile, this is adequate but not enriched.

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 description is a single, concise sentence with no filler or redundancy. It states the core purpose immediately and contains no unnecessary words, making it highly efficient for an agent to parse.

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

Completeness5/5

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

For a simple setter tool with complete parameter coverage and annotations, the description is fully sufficient. There is no output schema to document, and all required context is provided by the structured fields. The tool's low complexity does not demand additional explanatory content.

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 description coverage is 100%, with all four parameters clearly described (sourceName, filterName, filterEnabled, canvasUuid). The description does not add any additional semantic detail beyond what the schema provides, so the baseline score of 3 applies.

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?

The description 'Sets the enable state of a source filter' clearly identifies the action (sets) and the resource (source filter's enable state). It distinguishes from sibling tools like obs-set-source-filter-settings or obs-set-source-filter-name by focusing specifically on the enabled/disabled state. The verb is specific and the scope is unambiguous.

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?

The description provides no guidance on when to use this tool versus the many related filter tools (e.g., obs-set-source-filter-settings, obs-get-source-filter). It merely states the action without explaining contexts like toggling visibility or prerequisites (e.g., filter must exist). No exclusions or alternatives are mentioned.

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