Vobiz MCP Server

Official

by vobiz-ai

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Deafen a conference member

deafen_conference_member

DestructiveIdempotent

Deafen specified members in a live Vobiz conference so they stop hearing the room while others still hear them. Ideal for listen-only setups or private side conversations.

Instructions

Deafen members of a live Vobiz conference (POST /Conference/{name}/Member/{id}/Deaf/) so they stop hearing the room; others still hear them. Use it for listen-only setups or private side conversations. Pass one member_id, a comma-separated list, or all. Undo with undeafen_conference_member. A room that is not running, or a member who already left, returns the not_found error.

Input Schema

Name	Required	Description	Default
`member_id`	Yes	ConferenceMemberID from the ConferenceEnter callback (or get_conference), a comma-separated list such as 17,45,82, or `all` for every member.
`conference_name`	Yes	Conference room name, exactly as used in the <Conference> XML element.

Output Schema

Name	Required	Description
`ok`	No	True on success; false when the result is an error (then error, message and retryable are set).
`deaf`	No	New deaf state of the members (deafen and undeafen tools only).
`muted`	No	New mute state of the members (mute and unmute tools only).
`member_id`	No	Members the action was applied to: the literal "all", or the list of member IDs as Vobiz echoed them (or as requested).
`http_status`	No	HTTP status Vobiz answered with (202 = accepted, 204 = done).
`backend_message`	No	Vobiz's own status message, or null.
`conference_name`	No	Room the action was applied to.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.4.2Oct 21, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "backend_message": {
+      "description": "Vobiz's own status message, or null."
+    },
+    "conference_name": {
+      "description": "Room the action was applied to.",
+      "type": "string"
+    },
+    "deaf": {
+      "description": "New deaf state of the members (deafen and undeafen tools only).",
+      "type": "boolean"
+    },
+    "http_status": {
+      "description": "HTTP status Vobiz answered with (202 = accepted, 204 = done).",
+      "type": "number"
+    },
+    "member_id": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "items": {},
+          "type": "array"
+        }
+      ],
+      "description": "Members the action was applied to: the literal \"all\", or the list of member IDs as Vobiz echoed them (or as requested)."
+    },
+    "muted": {
+      "description": "New mute state of the members (mute and unmute tools only).",
+      "type": "boolean"
+    },
+    "ok": {
+      "description": "True on success; false when the result is an error (then error, message and retryable are set).",
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

First observedv1.1.1Oct 19, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=true, idempotentHint=true), and the description adds value beyond them: the exact semantic effect on audio flow, and the error behavior ('a room that is not running, or a member who already left, returns the not_found error'). Endpoint is disclosed too. Missing only auth/rate-limit context.

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?

Front-loads the action and its effect, then usage, then undo, then the error case. Every sentence earns its place with no redundancy.

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?

With an output schema present, return values need not be explained, and the description still covers the effect, batch semantics, undo path, and failure condition. Nothing an agent needs to invoke it correctly is missing.

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%, so the schema with its pattern and description already documents both parameters thoroughly. The description reinforces member_id's batch usage ('one member_id, a comma-separated list, or all') but adds no syntax or format beyond the schema, so baseline 3 applies.

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?

States a specific verb (Deafen) and resource (members of a live Vobiz conference) plus the exact effect: 'they stop hearing the room; others still hear them.' This effect clause cleanly distinguishes it from mute_conference_member, which the sibling list contains.

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

Usage Guidelines4/5

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

Gives concrete use cases ('listen-only setups or private side conversations') and names the inverse tool for undo ('undeafen_conference_member'). It does not explicitly contrast with mute_conference_member, but the stated effect implies the distinction, so the guidance is clear without being exhaustive.

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

Deploy Server