ServiceTitan MCP

scheduling_non_job_appointments_list

Read-onlyIdempotent

Retrieve a page of non-job appointments filtered by technician, timesheet code, schedule visibility, active status, start time, or created/modified timestamps.

Instructions

List one requested page of non-job appointments using IDs, technician, timesheet code, schedule visibility, active state, start bounds, and created or modified timestamps. Use scheduling_non_job_appointments_get for a known appointment; use dispatch appointment tools for appointments attached to jobs.

Input Schema

TableJSON Schema

Name	Required	Description
`ids`	No	Comma-separated IDs (maximum 50)
`page`	No	Page number (starts at 1)
`sort`	No	Sort: Field (default), +Field (asc), or -Field (desc). Fields: Id, CreatedOn, ModifiedOn
`pageSize`	No	Records per page (default 50)
`activeOnly`	No	Return active items only
`includeTotal`	No	Include total count in response
`technicianId`	No	Filter by technician ID
`createdBefore`	No	Return items created before this UTC timestamp
`modifiedBefore`	No	Return items modified before this UTC timestamp
`startsOnOrAfter`	No	Return items starting on or after this UTC timestamp
`timesheetCodeId`	No	Filter by timesheet code ID
`createdOnOrAfter`	No	Return items created on or after this UTC timestamp
`startsOnOrBefore`	No	Return items starting on or before this UTC timestamp
`modifiedOnOrAfter`	No	Return items modified on or after this UTC timestamp
`showOnTechnicianSchedule`	No	Filter by technician schedule visibility

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 destructiveHint, so the safety profile is covered. The description adds useful behavioral context by stating that the tool returns only one requested page, implying pagination rather than a full unfiltered dump, and clarifies the non-job scope.

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 accomplish both jobs: stating the action and filter surface, then disambiguating from related tools. The primary behavior is front-loaded and every clause 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?

Given the output schema is present, the 100% parameter documentation, and annotations covering read-only/idempotent behavior, the description adds the missing pieces: pagination semantics and sibling-tool routing. The agent has everything needed to select and call this tool correctly.

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 100%, so the schema already documents all 15 parameters in detail. The description groups parameters into categories like 'IDs, technician, timesheet code, schedule visibility, active state, start bounds, and created or modified timestamps,' but adds no new semantic detail beyond what the schema provides. 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 clearly identifies the operation as listing a page of non-job appointments and enumerates the main filter dimensions. It distinguishes itself from scheduling_non_job_appointments_get and dispatch appointment tools, so an agent can tell exactly which resource and scope this endpoint covers.

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 states when to use the sibling get tool for a known appointment and when to switch to dispatch appointment tools for job-attached appointments. This gives the agent unambiguous routing guidance without needing to inspect other tool schemas.

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

Deploy Server