Skip to main content
Glama
Sign In
Vobiz MCP Server

Vobiz MCP Server

Official
by vobiz-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List audio streams on a call

list_audio_streams
Read-only

Fetch all audio streams for a Vobiz call, including running and stopped, with status, WebSocket URL, track, and format. Use stream IDs or check what is still streaming; paginate with limit and offset.

Instructions

List the audio streams started on one Vobiz call (GET /Call/{uuid}/Stream/), running and stopped alike, with status, WebSocket URL, track and audio format. Use it to find stream_ids or check what is still streaming; for one stream's full record use get_audio_stream. Pagination is stateless: pass limit and offset on every call and continue with pagination.next_offset while has_more is true. An unknown call fails with not_found.

Input Schema

NameRequiredDescriptionDefault
limitNoStreams per page, max 100 (default 20).
offsetNoStreams to skip before the first returned (default 0); use pagination.next_offset from the previous page.
call_uuidYesUUID of the call whose streams to list: the request_uuid returned by make_call, or call_uuid from list_live_calls or list_call_records.

Output Schema

NameRequiredDescriptionDefault
okNotrue on success; false (with error and message) when the tool failed.
countNoStreams in this page.
streamsNoThe streams in this page.
call_uuidNoThe call that was queried.
paginationNoStateless paging block for the next call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.4.2
    • addedInput schema / properties / call_uuid / description
      Added value: +"UUID of the call whose streams to list: the request_uuid returned by make_call, or call_uuid from list_live_calls or list_call_records."
    • changedInput schema / properties / limit / description
      Previous value: -"Default 20."New value: +"Streams per page, max 100 (default 20)."
    • addedInput schema / properties / offset / description
      Added value: +"Streams to skip before the first returned (default 0); use pagination.next_offset from the previous page."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "call_uuid": {
+      "description": "The call that was queried.",
+      "type": "string"
+    },
+    "count": {
+      "description": "Streams in this page.",
+      "type": "number"
+    },
+    "ok": {
+      "description": "true on success; false (with error and message) when the tool failed.",
+      "type": "boolean"
+    },
+    "pagination": {
+      "additionalProperties": {},
+      "description": "Stateless paging block for the next call.",
+      "properties": {
+        "has_more": {
+          "description": "true when another page exists.",
+          "type": "boolean"
+        },
+        "limit": {
+          "description": "Page size used.",
+          "type": "number"
+        },
+        "next_offset": {
+          "description": "Offset for the next page, or null on the last page.",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "offset": {
+          "description": "Offset used.",
+          "type": "number"
+        },
+        "total": {
+          "description": "Total streams on the call, or null when Vobiz did not report it.",
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "streams": {
+      "description": "The streams in this page.",
+      "items": {
+        "additionalProperties": {},
+        "description": "The stream as Vobiz returns it: stream_id, status, service_url, audio_track, content_type, bidirectional, start and end time.",
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  2. First observedv1.1.1

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds meaningful behavior beyond them: pagination is stateless and limit/offset must be resent each call, continuation follows pagination.next_offset while has_more is true, and an unknown call fails with not_found. It stops short of auth/rate-limit context, so a 4 rather than 5.

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?

Front-loaded with the core action and scope, then alternatives, then pagination and error behavior, with no filler sentences. The first sentence is heavily parenthetical and slightly overpacked, but every clause carries information.

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, the description needn't enumerate return fields, and it still previews the useful ones (status, WebSocket URL, track, audio format). Purpose, routing to the sibling, pagination protocol, and failure mode are all covered.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3 and the schema already documents limit and offset. The description adds the cross-parameter continuation rule (pass both every call, resume from pagination.next_offset) that the schema alone does not express.

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 and resource ('List the audio streams started on one Vobiz call'), names the endpoint, and clarifies scope ('running and stopped alike'). It also names the sibling it is not (get_audio_stream), so an agent can distinguish the two without opening either schema.

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?

Gives explicit use cases ('find stream_ids or check what is still streaming') and an explicit alternative with its selecting condition ('for one stream's full record use get_audio_stream'). Nothing is left to inference.

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