Skip to main content
Glama
montrellcruse

ServiceTitan MCP Server (Enterprise)

dispatch_projects_list

Retrieve and filter dispatch projects in ServiceTitan using criteria like customer, technician, status, dates, and sorting options.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort: Field (default), +Field (asc), or -Field (desc). Fields: Id, ModifiedOn, CreatedOn, Name, TargetCompletionDate
idsNoComma-separated project IDs (maximum 50)
customerIdNoFilter by customer ID
locationIdNoFilter by location ID
projectTypeIdNoFilter by project type ID
invoiceIdNoFilter by invoice ID
technicianIdNoFilter by technician ID
jobIdNoFilter by job ID
appointmentIdNoFilter by appointment ID
projectManagerIdsNoComma-separated manager IDs
businessUnitIdsNoComma-separated business unit IDs
startsBeforeNoReturn projects starting before this UTC timestamp
startsOnOrAfterNoReturn projects starting on or after this UTC timestamp
completedBeforeNoReturn completed projects before this UTC timestamp
completedOnOrAfterNoReturn completed projects on or after this UTC timestamp
targetCompletionDateBeforeNoReturn projects with target completion before this UTC timestamp
targetCompletionDateOnOrAfterNoReturn projects with target completion on or after this UTC timestamp
statusNoProject status filter
externalDataApplicationGuidNoExternal data application GUID
externalDataKeyNoExternal data key
externalDataValuesNoExternal data values (comma-separated)
createdBeforeNoReturn items created before this UTC timestamp
createdOnOrAfterNoReturn items created on or after this UTC timestamp
modifiedBeforeNoReturn items modified before this UTC timestamp
modifiedOnOrAfterNoReturn items modified on or after this UTC timestamp
pageNoPage number (starts at 1)
pageSizeNoRecords per page (default 50)
includeTotalNoInclude total count in response
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/montrellcruse/servicetitan-mcp'

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