Skip to main content
Glama
Sign In
ServiceTitan MCP Server

ServiceTitan MCP Server

by Voryn-Software
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_campaign_costs

Retrieve marketing campaign costs with pagination and optional campaign ID filter.

Instructions

List marketing campaign costs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_campaign_costs"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
page_sizeNo
campaign_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations exist, so description carries full burden. The minimal text provides no behavioral details such as pagination, cost granularity, or data format.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise single sentence, but lacks structured information like usage conditions or examples. Could be more informative without adding length.

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

Completeness2/5

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

Despite having output schema and multiple sibling tools, description provides only a bare purpose. Lacks detail on pagination, filtering by campaign, and expected data shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and description adds no meaning to parameters (page, page_size, campaign_id). The description does not explain their purpose in listing costs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it lists marketing campaign costs, specifying the verb and resource. It distinguishes from sibling 'list_campaigns' which lists campaigns, not costs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives like list_campaigns or other list tools. No context on prerequisites or limitations.

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

Deploy Server

Other Tools