Skip to main content
Glama
Sign In
Vobiz MCP Server

Vobiz MCP Server

Official
by vobiz-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete a call recording

delete_recording
DestructiveIdempotent

Permanently deletes a specified call recording from a Vobiz account. Use it to remove an unwanted audio file, but note the recording cannot be restored afterward.

Instructions

Permanently delete one call recording from this Vobiz account (DELETE /Recording/{id}/). The audio file cannot be restored afterwards. To fetch or play a recording instead use get_call_recording; to find IDs use list_recordings. An ID that no longer exists fails with not_found. Gated by VOBIZ_ENABLE_PROVISIONING and confirm: true.

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true, set only after the user explicitly approved: permanently deleting this recording. If your client supports MCP elicitation, the server asks the user to approve directly and this flag is not relied on; otherwise it is your attestation that the user approved.
recording_idYesThe recording's ID, from list_recordings or get_call_recording.

Output Schema

NameRequiredDescriptionDefault
okNotrue on success; false (with error and message) when the tool failed.
deletedNotrue once Vobiz removed the recording.
http_statusNoHTTP status Vobiz answered with.
recording_idNoThe recording that was deleted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.4.2
    • changedInput schema / properties / confirm / description
      Previous value: -"Must be true, set only after the user explicitly approved: permanently deleting this recording."New value: +"Must be true, set only after the user explicitly approved: permanently deleting this recording. If your client supports MCP elicitation, the server asks the user to approve directly and this flag is not relied on; otherwise it is your attestation that the user approved."
    • addedInput schema / properties / recording_id / description
      Added value: +"The recording's ID, from list_recordings or get_call_recording."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "deleted": {
+      "description": "true once Vobiz removed the recording.",
+      "type": "boolean"
+    },
+    "http_status": {
+      "description": "HTTP status Vobiz answered with.",
+      "type": "number"
+    },
+    "ok": {
+      "description": "true on success; false (with error and message) when the tool failed.",
+      "type": "boolean"
+    },
+    "recording_id": {
+      "description": "The recording that was deleted.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. First observedv1.1.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, but the description adds meaningful context beyond them: irreversibility ('audio file cannot be restored afterwards'), the feature-flag gate, the confirm requirement, and the not_found error behavior. This is exactly the extra disclosure a mutation tool needs.

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 permanence, then adds alternatives, error behavior, and gating in tightly packed but non-redundant sentences. Every clause carries distinct information; nothing 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?

With an output schema present, return values need no explanation, and annotations plus 100% schema coverage handle safety and parameters. The description still covers irreversibility, gating, confirmation, alternatives, and error behavior, leaving no meaningful gap for an agent calling this tool.

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 description coverage is 100%, and the schema itself fully documents both confirm (approval attestation) and recording_id (source and pattern). The description only reiterates 'confirm: true' and the ID sources, so it adds little beyond the schema. Baseline 3 is appropriate.

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 ('Permanently delete one call recording') with the underlying API call, and explicitly distinguishes itself from sibling tools get_call_recording (fetch/play) and list_recordings (find IDs). An agent can tell exactly what this does and does not do without opening any 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?

Explicitly routes adjacent tasks to alternatives ('to fetch or play use get_call_recording; to find IDs use list_recordings') and states the gating condition (VOBIZ_ENABLE_PROVISIONING and confirm: true). It also notes the not_found failure for stale IDs, so the agent knows what happens when the precondition is wrong.

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