Skip to main content
Glama
Sign In
Vobiz MCP Server

Vobiz MCP Server

Official
by vobiz-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List recordings

list_recordings
Read-only

Retrieve call recordings for an account and sub-accounts, newest first, with recording URLs, call UUIDs, numbers, and duration. Filter by date and page through results.

Instructions

List call recordings on this account and its sub-accounts, newest first, with recording_url, call_uuid, numbers and duration (GET /Recording/). Optional from_date/to_date narrow by recording date; omitted, every recording is eligible. Vobiz returns at most 20 per page: pass limit and offset on every call (nothing is kept between calls) and follow pagination.next_offset until has_more is false. For the recordings of one known call use get_call_recording. Recording URLs give access to call audio, so share them only with the account owner.

Input Schema

NameRequiredDescriptionDefault
limitNoPage size, 1-20 (Vobiz caps a page at 20). Default 20.
offsetNoNumber of recordings to skip before the page starts (default 0). Pass pagination.next_offset from the previous page.
to_dateNoLatest recording date to include, YYYY-MM-DD; must not be before from_date.
from_dateNoEarliest recording date to include, YYYY-MM-DD.

Output Schema

NameRequiredDescriptionDefault
okNoTrue on success; false when the result is an error (then error, message and retryable are set).
countNoNumber of recordings on this page.
paginationNo
recordingsNoRecordings on this page, newest first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.4.2
    • changedInput schema / properties / from_date / description
      Previous value: -"Earliest recording date, YYYY-MM-DD."New value: +"Earliest recording date to include, YYYY-MM-DD."
    • changedInput schema / properties / limit / description
      Previous value: -"Max 20 (Vobiz limit). Default 20."New value: +"Page size, 1-20 (Vobiz caps a page at 20). Default 20."
    • addedInput schema / properties / offset / description
      Added value: +"Number of recordings to skip before the page starts (default 0). Pass pagination.next_offset from the previous page."
    • changedInput schema / properties / to_date / description
      Previous value: -"Latest recording date, YYYY-MM-DD."New value: +"Latest recording date to include, YYYY-MM-DD; must not be before from_date."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "count": {
+      "description": "Number of recordings on this page.",
+      "type": "number"
+    },
+    "ok": {
+      "description": "True on success; false when the result is an error (then error, message and retryable are set).",
+      "type": "boolean"
+    },
+    "pagination": {
+      "additionalProperties": {},
+      "properties": {
+        "has_more": {
+          "description": "True when another page exists.",
+          "type": "boolean"
+        },
+        "limit": {
+          "description": "Page size that was applied.",
+          "type": "number"
+        },
+        "next_offset": {
+          "description": "Offset to pass for the next page, or null on the last page.",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "offset": {
+          "description": "Offset that was applied.",
+          "type": "number"
+        },
+        "total": {
+          "description": "Total matching recordings, or null when Vobiz did not report it.",
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "recordings": {
+      "description": "Recordings on this page, newest first.",
+      "items": {
+        "description": "One recording as Vobiz returns it: recording_id, call_uuid, recording_url, from/to numbers, duration, file format and timestamps."
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  2. First observedv1.1.1

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is partly covered, but the description adds substantial non-obvious behavior: the 20-per-page cap, the statelessness ('nothing is kept between calls'), the required pagination loop until has_more is false, and a privacy caution about recording URLs granting access to call audio. Only the exact return shape is left implicit, and an output schema exists.

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?

Four dense sentences with the core action, filters, pagination mechanics, sibling alternative, and safety note each in their own place; scope and ordering are front-loaded and no sentence is filler.

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 an output schema exists, the description need not describe return values, and it covers everything else an agent needs: scope, ordering, filtering semantics, stateless pagination, termination condition, sibling alternative, and a security caveat.

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. The description goes beyond the schema by explaining that limit/offset must be re-passed on every call and that pagination.next_offset should be fed back until has_more is false, which is operational meaning the per-parameter text does not convey on its own.

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 with scope ('List call recordings on this account and its sub-accounts'), plus the ordering (newest first) and the exact fields returned. It explicitly distinguishes itself from the sibling get_call_recording, so an agent can route correctly 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 routing guidance: use this for account-wide listings, use get_call_recording 'for the recordings of one known call'. It also states the condition for date filtering ('omitted, every recording is eligible'), leaving nothing 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