ServiceTitan MCP

marketing_campaigns_costs_list

Read-onlyIdempotent

Retrieve marketing campaign costs for a required campaign ID, filter by year or month, and paginate or sort results to analyze spend per campaign.

Instructions

List one page of costs for a required campaign ID, optionally filtered by year or month. Use marketing_campaign_costs_list for a broader cost search across campaigns.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Campaign ID
`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)
`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.5/5.0

Behavior4/5

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

Annotations already cover read-only, non-destructive, and idempotent behavior. The description adds useful behavioral context beyond annotations by noting pagination ('one page') and optional year/month filtering. It does not over-explain, and the output schema exists to cover return details.

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 concise sentences with no filler. The core behavior is front-loaded, and the sibling distinction is provided in the second sentence. Every word adds value.

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 100% schema coverage, supportive annotations, and presence of an output schema, the description provides sufficient context for correct invocation. It communicates the essential scope, optional filters, pagination behavior, and names the relevant alternative without omitting critical information.

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 all seven parameters are already documented in the schema. The description reinforces that campaign ID is required and that year/month are optional filters, but it does not need to add further parameter-level meaning because the schema carries the full weight.

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 ('List'), a clear resource ('costs'), and the required scope ('for a required campaign ID'). It also explicitly contrasts with the sibling marketing_campaign_costs_list, so an agent can distinguish this per-campaign tool from the broader cross-campaign search tool.

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 clearly indicates this tool is for campaign-specific cost listing and explicitly points to marketing_campaign_costs_list when a broader cost search across campaigns is needed. This provides a direct when-to-use versus when-to-use-alternative signal.

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

Deploy Server