Skip to main content
Glama

toggle_mute

Mute or unmute a specific audio input in OBS Studio to control audio sources during streaming or recording.

Instructions

Toggle mute on an audio input.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
input_nameYesName of the audio input (from list_audio_inputs).

Implementation Reference

  • The handler implementation for the toggle_mute tool, which calls ToggleInputMute on the OBS client and returns the new muted state.
    case "toggle_mute": {
      await obs.call("ToggleInputMute", { inputName: args.input_name });
      const { inputMuted } = await obs.call("GetInputMute", {
        inputName: args.input_name,
      });
      return ok({ input: args.input_name, muted: inputMuted });
    }
  • The definition and registration of the toggle_mute tool within the tool declaration array.
    {
      name: "toggle_mute",
      description: "Toggle mute on an audio input.",
      inputSchema: {
        type: "object",
        properties: {
          input_name: {
            type: "string",
            description: "Name of the audio input (from list_audio_inputs).",
          },
        },
        required: ["input_name"],
      },
    },
Behavior3/5

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

With no annotations provided, the description carries full burden. The word 'Toggle' successfully conveys the state-flipping behavior (distinct from setting), but omits other mutation details like side effects, error conditions, or what determines current state.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise at 6 words with no filler. Front-loaded with the action verb. However, given zero annotations and the existence of `set_mute`, the brevity underserves the agent's need for behavioral context.

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

Completeness3/5

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

Adequate for a single-parameter toggle operation with complete schema coverage, but lacks critical sibling differentiation (`set_mute`) and output guidance given no output schema exists. Minimum viable but clear gaps remain.

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 coverage is 100% with the `input_name` parameter fully documented. Description mentions 'audio input' aligning with the schema but adds no additional semantic details (format constraints, validation rules) beyond what the schema already provides.

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?

The description uses specific verb 'Toggle' and resource 'audio input', clearly stating the operation. However, it fails to explicitly distinguish from sibling tool `set_mute` (toggle implies flipping state vs setting explicitly), preventing a 5.

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?

Description provides no guidance on when to use this tool versus `set_mute` or prerequisites like calling `list_audio_inputs` first. No contextual usage hints are provided.

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/LarsCanGit/OBS-MCP'

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