Skip to main content
Glama
Sign In
OBS MCP

OBS MCP

by Tom-R-Main
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

Get Source Filter List

obs-get-source-filter-list
Read-onlyIdempotent

Retrieves the list of filters applied to a specific source, returning an array of filter names and details for inspection or management.

Instructions

Gets an array of all of a source's filters

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

Input Schema

NameRequiredDescriptionDefault
canvasUuidNoUUID of the canvas containing the source
sourceNameYesName of the source

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 indicate readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered. Description adds that it returns an array, but does not mention error behavior (e.g., what happens if source is not found) or whether canvasUuid is optional. With annotations present, this is acceptable but minimal.

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?

Description is a single sentence, highly concise 'Gets an array of all of a source's filters'. No filler or repetition of the tool name. Perfectly efficient.

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?

Given good annotations (readOnly, idempotent), full schema coverage, and simple tool complexity (single required param), the description is sufficient. It clearly states the primary return type (array of filters). Missing minor details like 'all' implying completeness, but that's already in the description. No output schema, so no need to explain return structure beyond 'array'.

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 covers 100% of parameters with descriptions. The description adds no extra meaning beyond what the schema provides, so we use the baseline of 3. It doesn't clarify the role of canvasUuid (optional, for sources in specific canvas) or the format of sourceName beyond what the schema says.

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?

Description clearly states it gets an array of filters for a source. Differentiates from siblings like obs-get-filter-kind-list (lists filter types) and obs-get-source-filter (gets a specific filter), though could be more explicit about the distinction.

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 usage for retrieving filters of a source, which is clear from the tool name. However, it doesn't explicitly mention when to use this instead of obs-get-source-filter or obs-get-filter-kind-list, nor does it indicate prerequisites like the source must exist.

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