Skip to main content
Glama
JordanDalton

ServiceTitan MCP Server

services_create

Create new services in ServiceTitan by specifying tenant ID, service code, display name, and other details like pricing, warranty, categories, and more. Facilitates service management and customization.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountNoAccount Number
activeNoIs Active
addOnMemberPriceNoAdd-On Member Price
addOnPriceNoAdd-On Price
bonusNoBonus Amount
businessUnitIdNoBusiness Unit ID
categoryIdsNoArray of Category IDs
codeYesService Code
commissionBonusNoCommission Bonus Amount
costNoService Cost
crossSaleGroupNoCross-Sale Group
descriptionNoService Description
displayNameYesService Display Name
externalDataNoExternal Data Key-Value Pairs
externalIdNoExternal Service ID
hoursNoService Hours
isLaborNoIs Labor Service
memberPriceNoService Member Price
paysCommissionNoPays Commission
priceNoService Price
recommendationIdsNoArray of Recommendation IDs
soldByCommissionNoCommission Percentage
sourceNoService Source
taxableNoIs Taxable
tenantYesFormat - int64. Tenant ID
upgradeIdsNoArray of Upgrade IDs
warrantyDescriptionNoWarranty Description
warrantyDurationNoWarranty Duration
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JordanDalton/ServiceTitanMcpServer'

If you have feedback or need assistance with the MCP directory API, please join our Discord server