ServiceTitan MCP

marketing_scheduler_schedulersessions

Read-onlyIdempotent

List paginated sessions for a scheduler by ID, with optional filters on created or modified timestamps to locate specific records.

Instructions

List one page of sessions for a known scheduler, optionally filtered by created or modified timestamps. Use scheduler performance when aggregated metrics are needed.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Scheduler ID
`page`	No	Page number (starts at 1)
`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

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the description does not need to repeat those. It adds modest context by noting pagination and timestamp filtering, but does not disclose details like sort order, filter inclusivity, or response boundaries beyond what the schema and output schema likely cover.

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 no filler. The primary action and pagination behavior are front-loaded, and the alternative tool is mentioned in the second sentence without unnecessary detail.

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, paginated list tool with a rich output schema and strong annotations, the description is mostly sufficient. It covers the core purpose and the main alternative, but could be slightly more complete by addressing how to handle an unknown scheduler ID.

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 50%; page, pageSize, includeTotal, and id are documented in the schema. The description adds value by grouping the four timestamp parameters as 'created or modified timestamps,' but it does not clarify the exact semantics of before/on-or-after bounds.

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 states a specific verb ('List'), a concrete resource ('one page of sessions for a known scheduler'), and optional filtering behavior. It also differentiates from the sibling marketing_scheduler_scheduler_performance by noting that aggregated metrics belong there.

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

Usage Guidelines4/5

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

The description clearly indicates when to use the tool: listing sessions for a known scheduler. It also names an explicit alternative for aggregated metrics ('Use scheduler performance'), but does not mention how to discover a scheduler ID if unknown, such as via marketing_scheduler_schedulers.

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

Deploy Server