Skip to main content
Glama
JordanDalton

ServiceTitan MCP Server

jobs_get_list

Retrieve and filter job lists in ServiceTitan by tenant ID, status, priority, appointment dates, technician, customer, and other criteria to manage and analyze job data effectively.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appointmentStartsBeforeNoFormat - date-time (as date-time in RFC3339). Return jobs if any appointment starts after date/time (in UTC)
appointmentStartsOnOrAfterNoFormat - date-time (as date-time in RFC3339). Return jobs if any appointment starts after date/time (in UTC)
appointmentStatusNoFilters by appointment status. Return a job if it has any appointment with the specified status. Values: [Scheduled, Dispatched, Working, Hold, Done, Canceled]
bookingIdNoFormat - int64. Filters by booking ID that resulted in this job
businessUnitIdNoFormat - int64. Filters by job's business unit ID
campaignIdNoFormat - int64. Filters by job's campaign ID
completedBeforeNoFormat - date-time (as date-time in RFC3339). Return jobs that are completed before a certain date/time (in UTC)
completedOnOrAfterNoFormat - date-time (as date-time in RFC3339). Return jobs that are completed after a certain date/time (in UTC)
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 job's 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.
firstAppointmentStartsBeforeNoFormat - date-time (as date-time in RFC3339). Return jobs whose first appointment starts before date/time (in UTC)
firstAppointmentStartsOnOrAfterNoFormat - date-time (as date-time in RFC3339). Return jobs whose first appointment starts on or after date/time (in UTC). Use with "firstAppointmentStartsBefore" to find jobs whose first appointment is within the specified date range.
hasUnusedAppointmentsNoIf set to true, return jobs that have unused appointments.
idsNoPerform lookup by multiple IDs (maximum 50)
includeTotalNoWhether total count should be returned
invoiceIdNoFormat - int64. Filters by job's invoice ID
jobStatusNoFilters by job status Values: [Scheduled, Dispatched, InProgress, Hold, Completed, Canceled]
jobTypeIdNoFormat - int64. Filters by job type ID
locationIdNoFormat - int64. Filters by job's location ID
modifiedBeforeNoFormat - date-time (as date-time in RFC3339). Return items modified before certain date/time (in UTC)
modifiedOnOrAfterNoFormat - date-time (as date-time in RFC3339). Return items modified on or after certain date/time (in UTC)
numberNoFilters by job number
pageNoFormat - int32. The logical number of page to return, starting from 1
pageSizeNoFormat - int32. How many records to return (50 by default)
priorityNoFilters by priority. Supported priorities are "Low", "Normal", "High", "Urgent"
projectIdNoFormat - int64. Filters by project ID
soldByIdNoFormat - int64. Filters by the technician who sold the job
sortNoApplies sorting by the specified field: "?sort=+FieldName" for ascending order, "?sort=-FieldName" for descending order. Available fields are: Id, ModifiedOn, CreatedOn, Priority.
tagTypeIdsNoReturn jobs that have at least one of provided Tag Type assigned
technicianIdNoFormat - int64. Return jobs if technician is assigned to any appointment
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