ServiceTitan MCP

marketing_scheduler_schedulers

Read-onlyIdempotent

List marketing scheduler records by created or modified timestamps with pagination. Review scheduling history without modifying data.

Instructions

List one page of marketing scheduler records, optionally filtered by created or modified timestamps. Use marketing_scheduler_scheduler_performance for metrics about one known scheduler.

Input Schema

TableJSON Schema

Name	Required	Description
`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.4/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds the pagination limitation ('one page') and the filtering dimensions ('created or modified timestamps'), which are behavioral traits not expressed in the annotations. With an output schema present, the return shape does not need to be explained here.

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 purpose is stated first, and the routing to the alternative tool appears second. Every clause earns its place.

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, optionally filtered list tool with an output schema and strong annotations, the description covers the key call decision: list schedulers here, get metrics from performance. It leaves timestamp filter semantics largely to schema property names and does not disambiguate from the closely named marketing_scheduler_schedulersessions sibling, so a small completeness gap remains.

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 only 43%, leaving the four timestamp parameters undocumented in the schema. The description partially compensates by saying results are 'optionally filtered by created or modified timestamps', but it does not map those filters to specific parameter names or explain boundary semantics. Pagination parameters are already documented in the schema, so the description adds only modest value here.

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 opens with a specific verb and resource: 'List one page of marketing scheduler records'. It clearly identifies this as a paginated list endpoint and distinguishes it from the performance sibling by saying metric lookups belong on marketing_scheduler_scheduler_performance. There is no ambiguity about what object this tool operates on.

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 second sentence explicitly names the alternative tool and the condition for choosing it: 'Use marketing_scheduler_scheduler_performance for metrics about one known scheduler.' This gives an agent a clear decision rule: use this tool for listing/filtering scheduler records, and the sibling for metrics.

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

Deploy Server