ServiceTitan MCP

payroll_timesheets_job_list

Read-onlyIdempotent

Get a paginated list of timesheets for a given job ID, with filters by technician and dates for payroll review.

Instructions

List one requested page of timesheets attached to a required job. Use this when the job ID is known; use payroll_timesheets_jobs_list to search across optional comma-delimited job IDs.

Input Schema

TableJSON Schema

Name	Required	Description
`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
`endedOn`	No	Filter by ended-on date/time
`pageSize`	No	Records per page (default 50)
`startedOn`	No	Filter by started-on date/time
`includeTotal`	No	Include total count in response
`technicianId`	No	Technician ID
`createdBefore`	No
`modifiedBefore`	No
`createdOnOrAfter`	No
`modifiedOnOrAfter`	No

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.2/5.0

Behavior3/5

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

Annotations already carry the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false). The description adds pagination scoping ('one requested page'), which is behavioral context beyond the annotations, but does not detail filtering behavior, totals, or response shape. No contradiction with 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 zero waste: the first states the core purpose and scope, the second routes to the sibling alternative. The most decision-relevant information is front-loaded.

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

Completeness4/5

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

For a read-only, idempotent, paginated list with an output schema and safety annotations, the description is nearly complete for selection and invocation. The only notable gap is the absence of any description for the four date-filter parameters, which the schema only partially mitigates through names and formats.

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?

Schema covers 67% of parameters, so most of the semantic burden is carried by the schema. The description adds only marginal param-level meaning by anchoring jobId as the required discriminator; the four undocumented date filters (createdBefore, modifiedBefore, createdOnOrAfter, modifiedOnOrAfter) are not compensated for, though their names and formats are largely self-explanatory.

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?

States a specific verb (List), resource (timesheets attached to a job), and scope (one requested page, required job). Explicitly names payroll_timesheets_jobs_list as the sibling for multi-job searches, making the distinction unambiguous without needing to open either schema.

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?

Provides explicit when-to-use guidance: 'Use this when the job ID is known.' Names the alternative tool (payroll_timesheets_jobs_list) and the exact condition that selects it (searching across optional comma-delimited job IDs). Nothing is left to inference.

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

Deploy Server