Documentation
Comms
comms.get_call_analysis
REST
ShippingPOST /api/v1/comms/get_call_analysisMCP tool
Livecomms.get_call_analysisExposed on: REST API · Shop MCP server · Claude connector · Dash (in-app copilot) · Zapier. Part of the Comms domain.
Operating contract
The recap Service VIN already produced for one call: a summary of what happened, the caller's sentiment, the vehicle and name it heard, and the COMMITMENTS — the things somebody said they would do.
COMMITMENTS ARE THE VALUABLE PART and the reason this is not folded into comms.get_call. 'We'll call you back Thursday with a price' is the sentence that turns into a task and, if nobody reads it, into a lost job. Pair this with tasks.create anchored to the same conversation when a commitment needs someone to own it.
IT IS A MODEL'S READING OF A TRANSCRIPT, and it says so: sentiment is an inference, the name and vehicle are what was heard over a phone line, and a price in a summary is a paraphrase. Never quote a figure from here as the shop's price — read the quote (quotes.get) or ask.
analyzed_at is null when the call has not been analysed: too short, no transcript, or the analysis has not run yet. That is a normal answer and not an error. comms.get_call_transcript still has the raw words when the recap is missing.
Who may call it
- Permission
calls.accessThe caller must hold Calls at the ACT level. A read-only dashboard grant on the same section is refused.- Plan
- Every planNo plan gate. Available on every Service VIN plan.
- Retries
naturalNaturally idempotent — running it twice leaves the same world as running it once. A retrying integration needs no key.- Rate class
readCounted against the read budget — the widest of the four.
Input
| Field | Type | Description |
|---|---|---|
| callrequired | stringuuid | The call to read, as returned by comms.list_calls or comms.get_call. |
Output
| Field | Type | Description |
|---|---|---|
| call | string | — |
| summary | string | null | — |
| sentiment | string | null | — |
| analyzed_at | string | null | — |
| analysis | any | null | — |
Examples
Built from this capability's own schema — required fields and the ones carrying a default, and nothing invented. Paste one and it validates.
export SERVICEVIN_API_KEY=svk_live_…
curl -X POST https://www.servicevin.com/api/v1/comms/get_call_analysis \
-H "Authorization: Bearer $SERVICEVIN_API_KEY" \
-H "Content-Type: application/json" \
-d '{"call":"…"}'const res = await fetch("https://www.servicevin.com/api/v1/comms/get_call_analysis", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.SERVICEVIN_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({
"call": "…"
}),
});
// Success and failure are both envelopes. Switch on error.code, never
// on error.message — the codes are stable, the messages are for people.
const payload = await res.json();
if (!res.ok) throw new Error(payload.error.code);
const data = payload.data;import os, requests
res = requests.post(
"https://www.servicevin.com/api/v1/comms/get_call_analysis",
headers={"Authorization": f"Bearer {os.environ['SERVICEVIN_API_KEY']}"},
json={
"call": "…"
},
timeout=30,
)
payload = res.json()
if not res.ok:
raise RuntimeError(payload["error"]["code"])
data = payload["data"]{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "comms.get_call_analysis",
"arguments": {
"call": "…"
}
}
}Refusals
The four gates run in this order on every surface, and the order is not arbitrary — see Authentication.
| Status | Code | When |
|---|---|---|
| 404 | not_found | The id is unknown, or the feature is not enabled for this account. Deliberately the same answer for both. |
| 403 | forbidden | This login does not hold calls.access. |
| 422 | validation_error | An argument was wrong. The message names the field. |
| 429 | rate_limited | Too many read calls. Back off and retry. |
| 500 | internal_error | Something failed on our side. Nothing was changed. |