ServiceTitan MCP

marketing_calls_get

Read-onlyIdempotent

Retrieve a specific marketing call record by numeric ID, including all call details from ServiceTitan. Use when you have the call ID and need full record data.

Instructions

Retrieve one Marketing Calls v2 call record by numeric ID, including the call details returned by ServiceTitan. Use a call-list tool when the ID is unknown, and the recording or voicemail tools for those media resources.

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.3/5.0

Behavior3/5

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

The annotations already provide readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, covering the main safety profile. The description adds that the call details come from ServiceTitan, which is mild context, but it does not disclose any additional behavioral traits such as error behavior, availability, or data freshness.

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?

The description is two sentences long, concise, and front-loaded with the primary action. Every sentence earns its place: the first defines the operation and scope, the second provides alternative routing.

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 tool with a rich output schema and annotations already covering safety and idempotency, the description is complete. It also orients the agent toward the correct sibling tools when the ID is unknown or when media is needed.

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?

The input schema already fully documents the single 'id' parameter with description 'Call ID', so schema coverage is 100%. The description only reinforces that the ID is numeric and identifies a call record, adding no significant meaning beyond the schema.

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 states a specific verb ('Retrieve'), a specific resource ('one Marketing Calls v2 call record'), and the identifier type ('numeric ID'). It also distinguishes itself from list and media tools, making the tool's purpose unmistakable.

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 explicitly says to use a call-list tool when the ID is unknown and to use recording or voicemail tools for those media resources. This gives clear routing guidance, especially given the many marketing call sibling tools.

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

Deploy Server