ServiceTitan MCP

payroll_payroll_adjustments_list

Read-onlyIdempotent

Fetch a paginated list of payroll adjustments, filtering by employee IDs or posted date range to review or audit changes.

Instructions

List one requested page of payroll adjustments, optionally filtered by employee IDs and posted timestamp. Use payroll_payroll_adjustments_get for one known adjustment ID.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number (starts at 1)
`pageSize`	No	Records per page (default 50)
`employeeIds`	No	Comma-delimited employee IDs
`includeTotal`	No	Include total count in response
`postedOnOrAfter`	No	Filter adjustments posted on or after this UTC timestamp
`postedOnOrBefore`	No	Filter adjustments posted on or before 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.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is established. The description adds a useful pagination caveat ('one requested page') and filter scope, but does not provide deeper behavioral context such as defaults or edge cases; however, the output schema and annotations cover most of this.

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 front-loaded sentences with no filler. The first states the action and scope, and the second routes to the exact alternative, making it efficient for an agent to parse.

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 100% parameter schema coverage, strong safety annotations, an output schema, and an explicit sibling pointer, the description is complete enough for correct selection and invocation. Nothing critical 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?

All six parameters have descriptions in the input schema, so the schema carries the full semantic load. The free-text description mentions 'employee IDs and posted timestamp' filters and 'page' implicitly, but adds little beyond the schema's parameter descriptions.

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?

Description uses a specific verb ('List') with a clear resource ('payroll adjustments') and scope ('one requested page'), and explicitly names the sibling for fetching a single known adjustment. This makes it easy to distinguish from the get tool and other list endpoints.

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 directly states when to use the sibling alternative: 'Use payroll_payroll_adjustments_get for one known adjustment ID.' It also clarifies that this tool is for paginated listing with optional filters, giving agents enough context to choose between list and get.

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

Deploy Server