Skip to main content
Glama
JordanDalton

ServiceTitan MCP Server

projects_get_list

Retrieve a list of projects from ServiceTitan, filtered by criteria such as customer ID, location, project type, status, or date ranges. Supports pagination and sorting for efficient data access.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appointmentIdNoFormat - int64. Return project if it contains the specified appointment in the project's jobs
businessUnitIdsNoReturns projects which have at least one of the provided business units assigned
completedBeforeNoFormat - date-time (as date-time in RFC3339). Return projects that are completed before date
completedOnOrAfterNoFormat - date-time (as date-time in RFC3339). Return projects that are completed on or after date
createdBeforeNoFormat - date-time (as date-time in RFC3339). Return items created before certain date/time (in UTC)
createdOnOrAfterNoFormat - date-time (as date-time in RFC3339). Return items created on or after certain date/time (in UTC)
customerIdNoFormat - int64. Filters by customer ID
externalDataApplicationGuidNoFormat - guid. If this guid is provided, external data corresponding to this application guid will be returned.
externalDataKeyNoPerforms lookup by external data key, 'externalDataValues' must also be provided.
externalDataValuesNoPerforms lookup by external data values (maximum 50), 'externalDataKey' must also be provided.
idsNoPerform lookup by multiple IDs (maximum 50)
includeTotalNoWhether total count should be returned
invoiceIdNoFormat - int64. Return projects if it contains the specified invoice
jobIdNoFormat - int64. Return project if it contains the specified job
locationIdNoFormat - int64. Filters by location ID
modifiedBeforeNoFormat - date-time (as date-time in RFC3339). Return projects whose last modification date is before date
modifiedOnOrAfterNoFormat - date-time (as date-time in RFC3339). Return projects whose last modification date is on or after date
pageNoFormat - int32. The logical number of page to return, starting from 1
pageSizeNoFormat - int32. How many records to return (50 by default)
projectManagerIdsNoFilters by id of managers for matching project
projectTypeIdNoFormat - int64. Return projects if it contains the specified project type
sortNoApplies sorting by the specified field: "?sort=+FieldName" for ascending order, "?sort=-FieldName" for descending order. Available fields are: Id, ModifiedOn, CreatedOn, Name, TargetCompletionDate.
startsBeforeNoFormat - date-time (as date-time in RFC3339). Return projects that start before date
startsOnOrAfterNoFormat - date-time (as date-time in RFC3339). Return projects that start on or after date
statusNoReturns projects which have one of the provided statuses. "None" could be passed as one of the values to include projects without a status in the resulting collection.
targetCompletionDateBeforeNoFormat - date-time (as date-time in RFC3339). Return projects whose target completion date is before date
targetCompletionDateOnOrAfterNoFormat - date-time (as date-time in RFC3339). Return projects whose target completion date is on or after date
technicianIdNoFormat - int64. Return project if technician is assigned to any appointments on any job in the project
tenantYesFormat - int64. Tenant ID
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