ServiceTitan MCP

marketing_campaign_costs_list

Read-onlyIdempotent

Find marketing campaign costs by campaign ID, year, or month to track spending and inform budget decisions. Returns paginated results for easy review.

Instructions

Search campaign costs across campaigns by campaign ID, year, or month. Returns one page; use marketing_campaigns_costs_list when a specific campaign ID is the required path scope.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number (starts at 1)
`sort`	No	Sort: Field (default), +Field (asc), or -Field (desc). Fields: Id, Date
`year`	No	Cost year
`month`	No	Cost month
`pageSize`	No	Records per page (default 50)
`campaignId`	No	Campaign ID
`includeTotal`	No	Include total count in response

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?

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context like 'Returns one page' and the cross-campaign scope, but does not go deeper into pagination behavior, ordering, or omitted-records semantics. This is solid but not rich behavioral disclosure.

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, no filler, the core purpose is front-loaded, and the sibling distinction is packed into the second sentence. Every part earns its place.

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 read-only list/search tool with a full input schema, an output schema, and annotations covering safety, the description covers the essential behavior, pagination signal, and the relevant sibling alternative. Nothing critical is missing.

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 100%, so the schema already documents all 7 parameters. The description mentions campaign ID, year, and month, but these mirror the existing schema properties without adding new meaning, format details, or interaction notes.

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 and resource: 'Search campaign costs across campaigns by campaign ID, year, or month.' It clearly identifies the filtering dimensions and distinguishes itself from the sibling marketing_campaigns_costs_list by noting the path-scope difference.

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 explicitly provides a when-to-use versus alternative guidance: 'use marketing_campaigns_costs_list when a specific campaign ID is the required path scope.' This tells the agent exactly when not to select this tool.

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

Deploy Server