Skip to main content
Glama
montrellcruse

ServiceTitan MCP Server (Enterprise)

settings_tasks_list

List tasks with filters for status, dates, assignments, and more. Retrieve paginated task records with optional subtasks and total counts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoComma-separated task IDs
nameNoTask name filter
pageNoPage number (starts at 1)
sortNoSort: Field (default), +Field (asc), or -Field (desc). Fields: Id, CreatedOn, DescriptionModifiedOn, CompletedBy, Priority
jobIdNoJob ID
activeNoFilter by active statusTrue
isClosedNoDeprecated: filter by task closure state (use statuses when possible)
pageSizeNoRecords per page (default 50)
statusesNoComma-separated task statuses
jobNumberNoJob number
projectIdNoProject ID
customerIdNoCustomer ID
prioritiesNoComma-separated task priorities
taskNumberNoTask number
assignedToIdNoAssigned to employee ID
includeTotalNoInclude total count in response
reportedByIdNoReported by employee ID
createdBeforeNo
completeBeforeNoCompletion date upper bound (UTC)
modifiedBeforeNo
reportedBeforeNoReported date upper bound (UTC)
businessUnitIdsNoComma-separated business unit IDs
includeSubtasksNoInclude subtasks in each task payload
createdOnOrAfterNo
completeOnOrAfterNoCompletion date lower bound (UTC)
modifiedOnOrAfterNo
reportedOnOrAfterNoReported date lower bound (UTC)
employeeTaskTypeIdsNoComma-separated employee task type IDs
employeeTaskSourceIdsNoComma-separated employee task source IDs
involvedEmployeeIdListNoComma-separated involved employee IDs
employeeTaskResolutionIdsNoComma-separated employee task resolution IDs
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