Skip to main content
Glama
Giancarlo26

obs-action-history

by Giancarlo26

obs_input_property_items

Enumerate the actual device choices for an OBS source's dropdown property, returning the exact itemValue IDs needed to set input settings without guessing device paths or GUIDs.

Instructions

Enumerate the real choices behind a dropdown in a source's Properties dialog - every webcam, capture card, microphone, speaker and monitor this machine has, with the exact device ID string OBS wants written back. This is the difference between configuring OBS on a machine somebody already set up by hand and configuring one from nothing: without it, pointing a capture source at a camera means GUESSING a Windows device path, and pointing an audio source at a mic means guessing a GUID like '{0.0.1.00000000}.{xxxxxxxx-...}' that appears in no documentation and is different on every PC. Read the list here, then write the chosen itemValue with obs_set_input_settings under the SAME property name.

Write back itemValue, never itemName. itemName is the label a human reads ('Logitech StreamCam'); itemValue is the device path, and it is what OBS matches on. itemEnabled false means the device is known to OBS but not selectable right now - typically another application holds it open.

propertyName is the plugin's INTERNAL id, not the label in the dialog. Verified on the reference machine: dshow_input (webcam / capture card): video_device_id, audio_device_id, res_type, resolution, video_format, color_space wasapi_input_capture and wasapi_output_capture (mic / desktop audio): device_id monitor_capture (screen): monitor_id, method Other kinds and other plugins have their own ids; the two failure messages tell them apart. 'Unable to find a property by that name' means the id is wrong. 'The property found is not a list' means the id is RIGHT but that property is a button, a checkbox, a path or a text box - which is itself useful, because it is how you confirm a button exists before pressing it with obs_press_input_button.

These values are not portable and not permanent: a USB camera moved to a different port gets a different video_device_id, which is the usual reason a scene that worked yesterday shows a black rectangle today. Re-read this list rather than reusing a stored string.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputNameYesExact existing input name, as returned by obs_list_inputs. The source must already exist - this reads the properties of an instance, not of a kind.
propertyNameYesInternal property id, e.g. 'video_device_id' for a webcam or 'device_id' for a mic.
Behavior5/5

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

No annotations are provided, so the description carries the full burden. It fully discloses behavior: returns a list of itemName/itemValue, explains itemEnabled=false semantics, emphasizes that itemValue (not itemName) is what OBS matches, and notes that values are not portable or permanent (USB port change). It also clarifies that it reads properties of an existing instance, not a kind.

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?

Though lengthy, the description is efficiently structured: purpose, usage guidance, parameter specifics, and caveats. Every sentence adds critical context—there is no filler. The structure is logical and front-loaded with the primary usage; the detailed device ID list and failure messages are directly actionable.

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?

Given the complexity of OBS internals and the absence of an output schema, the description is remarkably complete. It explains exactly what is returned (itemName/itemValue), how to interpret itemEnabled, and how to use the result with obs_set_input_settings. It covers portability and the effect of device changes on stored IDs, eliminating guesswork for the agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Both parameters have schema descriptions, but the description adds significant depth. It explains that propertyName is the internal ID and provides a verified list of IDs for different input types (dshow_input, wasapi_input_capture, monitor_capture). It also clarifies that inputName must be an exact existing input name and that the source must already exist. This goes well beyond the basic field descriptions.

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 is extremely specific: it enumerates the selectable device options (webcams, mics, etc.) for a given input property, with exact device IDs. It clearly distinguishes itself from sibling tools like obs_list_inputs (lists inputs) and obs_set_input_settings (writes settings), and explains exactly what value to extract for later use.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use it ('Read the list here, then write the chosen itemValue with obs_set_input_settings'), contrasts it with the guesswork without it, and gives detailed failure-mode guidance ('Unable to find a property by that name' vs 'The property found is not a list') to help diagnose wrong vs right property IDs. It also warns against reusing stored values.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Giancarlo26/obs-action-history'

If you have feedback or need assistance with the MCP directory API, please join our Discord server