ServiceTitan MCP

dispatch_job_splits_list

Read-onlyIdempotent

List job split records for a specific job ID, filtering by active status and created or modified timestamps. Use pagination to browse through one page of results at a time.

Instructions

List one page of split records for a single required job ID, with activity and date filters. Use dispatch_job_splits_by_jobs_list to query splits across multiple jobs.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No	Page number (starts at 1)
`sort`	No	Sort: Field (default), +Field (asc), or -Field (desc). Fields: Id, ModifiedOn, CreatedOn
`jobId`	Yes	Job ID
`active`	No	Filter by active status	True
`pageSize`	No	Records per page (default 50)
`includeTotal`	No	Include total count in response
`createdBefore`	No	Return items created before this UTC timestamp
`modifiedBefore`	No	Return items modified before this UTC timestamp
`createdOnOrAfter`	No	Return items created on or after this UTC timestamp
`modifiedOnOrAfter`	No	Return items modified on or after this UTC timestamp

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv3.0.0Sep 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {},
+  "type": "object"
+}

First observedv2.5.1Apr 18, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds useful behavioral context beyond those: pagination ('one page'), the required single-job scope, and available filter dimensions. This supplements rather than contradicts the annotations.

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

Conciseness5/5

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

Two sentences with no wasted words. The essential scope and pagination behavior are front-loaded, and the sibling-tool differentiation is placed second for quick routing.

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

Completeness5/5

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

Given the rich 100%-covered input schema, detailed annotations, and an output schema, the description provides the additional context an agent needs: pagination behavior, single-job requirement, and the multi-job alternative. Nothing essential is missing.

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

Parameters3/5

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

The input schema has 100% parameter description coverage, so the schema carries the full meaning of jobId, page, sort, active, pageSize, and date filters. The description groups these as 'activity and date filters' but adds no new detail beyond what the schema already provides, so baseline 3 is appropriate.

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

Purpose5/5

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

The description uses a specific verb ('List'), names the resource ('split records'), and states a clear scope ('for a single required job ID'). It also explicitly distinguishes itself from the sibling tool dispatch_job_splits_by_jobs_list, which handles multiple jobs.

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

Usage Guidelines5/5

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

The description clearly states when to use this tool: for one page of splits for a single required job ID. It also names the alternative tool for querying splits across multiple jobs, giving the agent an explicit routing decision.

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

Deploy Server