Skip to main content
Glama
Sign In
OBS MCP

OBS MCP

by Tom-R-Main
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

Remove Source Filter

obs-remove-source-filter
DestructiveIdempotent

Remove a filter from an OBS source. Provide the source name and filter name to delete the specified filter from your scene.

Instructions

Removes a filter from a source

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>"
    },
    "name": "obs-remove-source-filter"
  }
}

Input Schema

NameRequiredDescriptionDefault
canvasUuidNoUUID of the canvas containing the source
filterNameYesName of the filter to remove
sourceNameYesName of the source the filter is on

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, covering the safety profile. The description adds no further behavioral details (e.g., permanence, handling of nonexistent filters), but it does not contradict the annotations, so a mid-range score is appropriate.

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 clear sentence with no unnecessary words, perfectly sized for the tool's simplicity.

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?

For a simple delete operation with complete schema and appropriate annotations, the description is mostly sufficient. It could optionally mention behavior when the filter doesn't exist or clarify the optional canvasUuid parameter, but these are minor gaps given the schema covers parameter semantics.

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?

The input schema provides complete descriptions (100% coverage) for all three parameters, so the description adds no extra meaning. The baseline of 3 applies since the schema does the heavy lifting.

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 'Removes a filter from a source' uses a specific verb ('removes') and resource ('filter', 'source') making the action unambiguous. It clearly distinguishes from sibling tools like obs-create-source-filter or obs-set-source-filter-enabled.

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 is provided about when to use this tool versus alternatives like disabling a filter or clearing its settings. The description simply states the action without context, prerequisites, or exclusions.

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