Skip to main content
Glama
montrellcruse

ServiceTitan MCP

by montrellcruse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

payroll_timesheets_jobs_list

Read-onlyIdempotent

Retrieve a page of job timesheets across selected jobs, with filters for job IDs, start/end dates, technician, and sorting to locate payroll records.

Instructions

List one requested page of job timesheets across jobs, optionally filtered by comma-delimited job IDs. Use payroll_timesheets_job_list when retrieving timesheets for one required job.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (starts at 1)
sortNoSort: Field (default), +Field (asc), or -Field (desc). Fields: Id, ModifiedOn, CreatedOn
jobIdsNoComma-delimited job IDs
endedOnNoFilter by ended-on date/time
pageSizeNoRecords per page (default 50)
startedOnNoFilter by started-on date/time
includeTotalNoInclude total count in response
technicianIdNoTechnician ID
createdBeforeNo
modifiedBeforeNo
createdOnOrAfterNo
modifiedOnOrAfterNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {},
+  "type": "object"
+}
  2. First observedv2.5.1

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful scoping context ('across jobs', 'one requested page') but does not disclose further behavioral details such as response size limits or how filters interact. This is adequate but not rich.

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 tight sentences with no filler. The core action and scope are front-loaded, and the sibling distinction is given in the second sentence. Every word earns its place.

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?

With a rich input schema, an output schema, and annotations covering read-only and idempotent behavior, the description provides enough context for an agent to invoke the tool correctly. It names the key filter, clarifies pagination, and routes single-job requests to the right sibling.

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 description coverage is 67%, which is moderate. The description reinforces the jobIds parameter by saying 'comma-delimited job IDs' and clarifies pagination with 'one requested page,' but it does not add meaning to the four undocumented date parameters or other fields. The schema still carries most of the parameter documentation burden.

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 and resource: 'List one requested page of job timesheets across jobs.' It clearly distinguishes this tool from payroll_timesheets_job_list by framing this as the multi-job variant and noting the single-job sibling. An agent can select correctly without opening 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?

The description explicitly names the alternative tool and the condition that selects it: 'Use payroll_timesheets_job_list when retrieving timesheets for one required job.' This implies this tool is for retrieving timesheets across multiple jobs, giving the agent an actionable routing rule.

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

Deploy Server

Other Tools