ServiceTitan MCP

payroll_timesheet_codes_list

Read-onlyIdempotent

Retrieve timesheet codes in paginated pages and apply filters for active status, creation or modification dates, and sorting to locate the payroll codes you need.

Instructions

Retrieve one requested page of timesheet codes. Use the available filters to narrow results and request subsequent pages explicitly.

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
`active`	No	Filter by active status	True
`pageSize`	No	Records per page (default 50)
`includeTotal`	No	Include total count in response
`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

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false. The description adds one useful behavioral trait beyond annotations: the caller must explicitly request each page and should not expect automatic iteration. No contradiction exists, but the description does not add much additional behavioral context beyond paging.

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?

The description is one compact two-sentence definition with the core action front-loaded and no redundant phrasing. Every clause adds useful information: the resource, page semantics, filtering capability, and explicit pagination expectation.

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

Completeness3/5

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

For a paginated read-only list tool with an output schema and safety-bearing annotations, the description conveys the essential paging behavior and filter availability. However, given the large sibling set and the presence of four loosely documented date params, the description could usefully mention sort/filter semantics or point to export/get alternatives for other retrieval needs.

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

Parameters2/5

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

Schema description coverage is only 56%, and the description merely says to use 'available filters' without identifying which filters matter or how date-based filters behave. The schema describes page, sort, active, pageSize, and includeTotal, but the four date parameters remain semantically undocumented, and the description does not compensate for that gap.

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

Purpose4/5

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

The description states a specific action ('Retrieve'), a resource ('timesheet codes'), and a key scope ('one requested page'), so an agent can tell this is a paginated list operation. It does not explicitly contrast with sibling tools like payroll_timesheet_codes_get or export_timesheet_codes, but the page-focused wording makes the listing role clear.

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

Usage Guidelines2/5

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

The description gives tactical guidance on using filters and requesting pages, but it does not explain when to choose this tool over nearby alternatives such as payroll_timesheet_codes_get for a single code or export_timesheet_codes for bulk retrieval. No exclusions or alternative-selection conditions are provided.

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

Deploy Server