Skip to main content
Glama
vobiz-ai

Vobiz MCP Server

Official
by vobiz-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Mute a conference member

mute_conference_member
DestructiveIdempotent

Silence one or more live conference members so others cannot hear them while they still hear the room. Restore audio later by unmuting them.

Instructions

Mute one or more members of a live Vobiz conference (POST /Conference/{name}/Member/{id}/Mute/) so others cannot hear them; they still hear the room. Pass one member_id, a comma-separated list, or all (for example presenter mode). Undo with unmute_conference_member. A room that is not running, or a member who already left, returns the not_found error.

Input Schema

NameRequiredDescriptionDefault
member_idYesConferenceMemberID from the ConferenceEnter callback (or get_conference), a comma-separated list such as 17,45,82, or `all` for every member.
conference_nameYesConference room name, exactly as used in the <Conference> XML element.

Output Schema

NameRequiredDescriptionDefault
okNoTrue on success; false when the result is an error (then error, message and retryable are set).
deafNoNew deaf state of the members (deafen and undeafen tools only).
mutedNoNew mute state of the members (mute and unmute tools only).
member_idNoMembers the action was applied to: the literal "all", or the list of member IDs as Vobiz echoed them (or as requested).
http_statusNoHTTP status Vobiz answered with (202 = accepted, 204 = done).
backend_messageNoVobiz's own status message, or null.
conference_nameNoRoom the action was applied to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.2
    • 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"
+}
  2. First observedv1.1.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare idempotent/destructive/openWorld, so the bar is lower. The description adds real value beyond them: the asymmetric audio effect (muted members still hear the room) and the failure behavior (non-running room or departed member returns not_found). Does not document rate limits or return shape, but output schema covers returns.

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?

A single front-loaded paragraph: purpose and effect first, then accepted inputs, then the undo path, then error behavior. Dense but every sentence carries information; the parenthetical endpoint is slightly extraneous for an agent that only invokes the tool.

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 annotations conveying the safety profile, a 100%-covered schema for both params, and an output schema for returns, the description covers everything else the agent needs: side effect on audio, bulk semantics, the counter-tool, and failure conditions.

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% and the member_id description already documents the accepted forms, so the description largely restates rather than adds. The 'presenter mode' framing for 'all' gives minor extra intent context, but no new syntax or edge-case meaning beyond the schema.

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 (mute) and resource (conference members) plus the exact effect: 'so others cannot hear them; they still hear the room.' This distinguishes it from sibling tools like deafen_conference_member (which targets hearing) and kick/hangup (which remove).

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?

Explicitly routes the agent for the undo case ('Undo with unmute_conference_member') and describes the member_id forms (single, comma-list, all). It stops short of contrasting with related siblings such as deafen or kick when the intent is to remove rather than silence a participant.

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