ServiceTitan MCP

marketing_campaigns_list

Read-onlyIdempotent

Search marketing campaigns by ID, name, phone number, active status, or creation and modification date ranges. Returns one page of matching campaigns to review and act on.

Instructions

Search campaigns by IDs, name, phone number, active state, or created and modified ranges. Returns one page; use marketing_campaigns_get for a known campaign ID.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ids`	No	Comma-delimited campaign IDs
`name`	No	Campaign name filter
`page`	No	Page number (starts at 1)
`sort`	No	Sort: Field (default), +Field (asc), or -Field (desc). Fields: Id, Name, CreatedOn, ModifiedOn
`active`	No	Filter by active status	True
`pageSize`	No	Records per page (default 50)
`includeTotal`	No	Include total count in response
`createdBefore`	No
`modifiedBefore`	No
`createdOnOrAfter`	No
`modifiedOnOrAfter`	No
`campaignPhoneNumber`	No	Campaign phone number filter

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

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description aligns with those hints. The added 'Returns one page' clause discloses pagination behavior beyond the annotations, though it does not clarify how multiple filters combine.

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 filter scope is front-loaded, followed by the return behavior and sibling routing, making it easy for an agent to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter read-only list tool with an output schema and safety annotations, the description covers the essential searchable criteria, signals one-page responses, and routes known-ID lookups to marketing_campaigns_get. Minor omissions like exact date-range semantics and filter combination behavior are either self-evident from property names or not critical given the schema coverage.

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?

Schema coverage is 67%, and the description adds a useful high-level grouping of the key filter parameters, including the four otherwise undocumented date-time fields under 'created and modified ranges.' It does not add detail for paging or sorting, but the schema already describes page, pageSize, sort, and includeTotal.

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 action, 'Search campaigns', and enumerates the supported filter dimensions: IDs, name, phone number, active state, and created/modified ranges. It also explicitly distinguishes itself from marketing_campaigns_get by directing known-ID lookups to that sibling.

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?

The description gives explicit when-to-use guidance: use this tool for searching/filtering campaigns and use marketing_campaigns_get for a known campaign ID. It also notes that the tool returns one page, setting expectations for paginated list usage.

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

Deploy Server