ServiceTitan MCP

marketing_calls_recording_get

Read-onlyIdempotent

Retrieve the audio recording for a known Marketing Calls v2 call ID. Returns client-decoded audio data; use a binary-capable client if faithful bytes are required.

Instructions

Request the audio recording for a known Marketing Calls v2 call ID. ServiceTitan documents an audio/mpeg stream, but this wrapper delivers client-decoded data through its standard JSON/text envelope; use a binary-capable API client when faithful audio bytes are required. Use marketing_calls_get for the call record itself.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Call ID

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv3.0.0Sep 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {},
+  "type": "object"
+}

First observedv2.5.1Apr 18, 2026

TDQS

A4.9/5.0

Behavior5/5

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

The description goes beyond the readOnly/idempotent annotations by disclosing a critical behavioral trait: although ServiceTitan documents an audio/mpeg stream, this wrapper delivers client-decoded data through its JSON/text envelope. This tells the agent that raw binary fidelity is not guaranteed, which is exactly the kind of behavioral context needed.

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?

Three sentences, each earning its place: the first states the operation, the second gives the critical binary-format caveat, and the third routes to the sibling tool. The information is front-loaded and there is no redundant or filler text.

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?

For a single-parameter read-only tool with an output schema and annotations covering safety and idempotency, the description provides the missing operational details: the expected ID source, the JSON/text envelope behavior, and the sibling alternative. Nothing essential is left for the agent to guess.

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?

The schema already documents the single 'id' parameter at 100% coverage, so the baseline is 3. The description adds useful semantic context by specifying that the ID must be a known Marketing Calls v2 call ID, which clarifies the expected ID source beyond the generic schema text 'Call ID.'

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?

The description uses a specific verb and resource: 'Request the audio recording for a known Marketing Calls v2 call ID.' It also distinguishes itself from marketing_calls_get by telling the agent to use that sibling for the call record itself, so the tool's purpose is unambiguous.

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?

It gives clear context for invocation ('for a known Marketing Calls v2 call ID'), explicitly names the alternative for related data ('Use marketing_calls_get for the call record itself'), and warns when this wrapper is not appropriate ('use a binary-capable API client when faithful audio bytes are required'). This is strong routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server