Vobiz MCP Server

Official

by vobiz-ai

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Get call recording

get_call_recording

Read-only

Find recordings of a specific call by call UUID or recording ID, returning metadata and recording URLs.

Instructions

Find the recording(s) of one call on this account and return their metadata and recording_url (GET /Recording/). Pass exactly one of call_uuid (every recording of that call, up to 20) or recording_id (that one recording). Not every call is recorded: an unrecorded or unknown call_uuid returns ok with count 0, while an unknown recording_id returns the not_found error. To browse recordings across calls or by date use list_recordings. Recording URLs give access to call audio, so share them only with the account owner.

Input Schema

Name	Required	Description	Default
`call_uuid`	No	UUID of the call whose recordings to find. Leave out when passing recording_id.
`recording_id`	No	ID of one recording, as returned by list_recordings or a recording callback. Leave out when passing call_uuid.

Output Schema

Name	Required	Description
`ok`	No	True on success; false when the result is an error (then error, message and retryable are set).
`note`	No	Present when no recording exists for the call.
`count`	No	Number of recordings returned (0 when the call was not recorded).
`call_uuid`	No	Echo of the call_uuid that was searched, when that form was used.
`recordings`	No	The recordings found, each with its recording_url.
`recording_id`	No	Echo of the recording_id that was fetched, when that form was used.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.4.2Oct 21, 2026

changedInput schema / properties / call_uuid / description

Previous value: -"UUID of the call whose recordings to find."New value: +"UUID of the call whose recordings to find. Leave out when passing recording_id."

changedInput schema / properties / recording_id / description

Previous value: -"A specific recording ID."New value: +"ID of one recording, as returned by list_recordings or a recording callback. Leave out when passing call_uuid."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "call_uuid": {
+      "description": "Echo of the call_uuid that was searched, when that form was used.",
+      "type": "string"
+    },
+    "count": {
+      "description": "Number of recordings returned (0 when the call was not recorded).",
+      "type": "number"
+    },
+    "note": {
+      "description": "Present when no recording exists for the call.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "True on success; false when the result is an error (then error, message and retryable are set).",
+      "type": "boolean"
+    },
+    "recording_id": {
+      "description": "Echo of the recording_id that was fetched, when that form was used.",
+      "type": "string"
+    },
+    "recordings": {
+      "description": "The recordings found, each with its recording_url.",
+      "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"
+}

First observedv1.1.1Oct 19, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations declare read-only/open-world, but the description adds non-obvious behavior the annotation cannot: unrecorded or unknown call_uuid returns ok with count 0 while an unknown recording_id returns not_found, and the cardinality cap of 20. It also flags the security sensitivity of recording URLs.

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 verb+resource+endpoint, then the parameter rule, then edge-case return behavior, then the alternative tool, then the security caveat. Dense but every sentence earns its place with no 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?

With an output schema present, return-shape detail is not needed, and the description still covers selection rules, edge-case responses, sibling routing, and the sensitive-data caveat. Fully sufficient for an agent to call it correctly.

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 coverage is 100% so the parameter docs already exist, but the description adds meaning beyond the schema by stating cardinality ('every recording of that call, up to 20' for call_uuid vs 'that one recording' for recording_id) and the mutual-exclusivity rule, which the schema only hints at.

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 ('find the recording(s)'), the exact resource ('of one call on this account'), and what is returned ('metadata and recording_url'), plus the underlying GET /Recording/ endpoint. It is clearly distinguishable from list_recordings and get_call_details.

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 the explicit selection rule ('pass exactly one of call_uuid or recording_id') with the semantic difference between them, and names the alternative tool and its condition ('to browse recordings across calls or by date use list_recordings'). 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