OBS MCP

Get filter settings

get_filter_settings

Retrieve the settings and current state of a specific filter applied to an OBS source.

Instructions

Get the settings and state of one filter on 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": {
      "source_name": "<source_name>",
      "filter_name": "<filter_name>"
    },
    "name": "get_filter_settings"
  }
}

Input Schema

Name	Required	Description	Default
`filter_name`	Yes
`source_name`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 14, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. 'Get' implies a read-only operation, and 'settings and state' hints at the return content, but the description does not explicitly state that it has no side effects, does not require special permissions, or describe error behavior if the filter/source doesn't exist. It is minimally adequate.

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 that front-loads the action and resource, with no wasted words or redundancy.

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 get operation with an output schema present (so return values need not be detailed), the description adequately covers the essential context. It lacks comparison to sibling tools but is otherwise complete for the tool's simplicity.

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 0% and the description compensates only slightly by indicating that the tool operates on 'one filter on a source,' mapping loosely to the filter_name and source_name parameters. The parameter names themselves are self-explanatory, but no additional meaning, constraints, or examples are provided.

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 uses the specific verb 'Get' and identifies the resource as 'the settings and state of one filter on a source.' This clearly distinguishes it from sibling tools like list_filters (which lists filters), set_filter_settings (which modifies), and toggle_filter (which toggles state). It is both specific and differentiated.

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?

The description implies its usage by naming the object, but it does not explicitly state when to use this tool versus alternatives such as list_filters for enumerating filters or set_filter_settings for modifying them. No exclusions or prerequisites are mentioned, so guidance is only implied.

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

Deploy Server