ServiceTitan MCP

marketing_calls_v3_list

Read-onlyIdempotent

Search marketing calls by ID, caller number, agent, campaign, duration, call dates, or active status. Get a single page of matching results for ordinary call lookup.

Instructions

Search calls through Marketing Calls v3 using comma-delimited IDs, caller number, active state, agents, campaign, duration, timestamps, or sort. Returns one page; prefer this for ordinary call search, and use v2 only for its numeric ID array, activeOnly, or orderBy contract.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ids`	No	Comma-delimited call IDs
`page`	No	Page number (starts at 1)
`sort`	No	Sort: Field (default), +Field (asc), or -Field (desc). Fields: Id, CreatedOn, ModifiedOn
`active`	No	Filter by active status	True
`agentId`	No	Agent ID
`pageSize`	No	Records per page (default 50)
`agentName`	No	Agent name
`campaignId`	No	Campaign ID
`minDuration`	No	Minimum duration in seconds
`createdAfter`	No	Created after UTC timestamp
`includeTotal`	No	Include total count in response
`createdBefore`	No
`modifiedAfter`	No	Modified after UTC timestamp
`modifiedBefore`	No
`agentExternalId`	No	Agent external ID
`agentIsExternal`	No	Whether agent is external
`createdOnOrAfter`	No
`callerPhoneNumber`	No	Caller phone number
`modifiedOnOrAfter`	No
`phoneNumberCalled`	No	Phone number called

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

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds pagination behavior ('Returns one page') and clarifies v2's differing contract, which are useful details beyond the annotations. It does not contradict the annotations.

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?

Two sentences with no filler. The core purpose and one-page behavior are front-loaded, followed by a concise recommendation that routes the agent away from the v2 sibling when appropriate.

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?

Given the rich schema (20 optional parameters, 80% coverage), annotations covering safety, and an output schema, the description supplies what is missing: the intended use case, pagination note, and v2-vs-v3 selection guidance. Return-value details are already handled by the output schema.

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 high (80%), so the schema already documents each parameter in detail. The description groups filters into categories like 'comma-delimited IDs, caller number, active state, agents, campaign, duration, timestamps, or sort,' but this adds little semantic value 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 clear verb ('Search') and resource ('calls through Marketing Calls v3') and enumerates the major filter dimensions. It also explicitly differentiates from marketing_calls_v2_list by naming the v2-only contract, so an agent can distinguish sibling list tools.

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 explicit routing guidance: 'prefer this for ordinary call search, and use v2 only for its numeric ID array, activeOnly, or orderBy contract.' This tells the agent when to select this tool over its direct sibling and what conditions should route to v2.

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

Deploy Server