ServiceTitan MCP

memberships_recurring_service_events_list

Read-onlyIdempotent

List recurring-service events filtered by IDs, status, job, location, and created or modified timestamps. Retrieve a specific page to review follow-up statuses and event records.

Instructions

List one requested page of recurring-service events using event IDs, status, job, location, and created or modified timestamp filters. Use memberships_recurring_services_get for the parent service record; use job tools for a job referenced by an event.

Input Schema

TableJSON Schema

Name	Required	Description
`ids`	No	Comma-separated recurring service event IDs (maximum 50)
`page`	No	Page number (starts at 1)
`jobId`	No	Filter by job ID
`status`	No	Filter by recurring service event follow-up status
`pageSize`	No	Records per page (default 50)
`locationId`	No	Filter by location ID
`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

A3.8/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 covered. The description adds that the operation returns one requested page and supports timestamp/status/job/location/ID filters, but it does not disclose ordering, pagination conventions, or time-zone semantics. This is acceptable 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 sentences front-load the operation and filter scope, then add routing guidance. Every sentence earns its place with no repetition of the schema.

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 list operation with an output schema and safety annotations, the description covers the page, filter dimensions, and the most relevant sibling routing. It does not describe the event concept or the exact parent-service list alternative, but nothing essential is missing for invoking the tool. The 11 optional parameters make this a slightly complex tool, and the description handles that reasonably.

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?

With 64% schema description coverage, the schema documents most parameters, and the description adds a useful summary of the filter dimensions (IDs, status, job, location, created/modified timestamps). The four date-only parameters still rely on their format field plus the description's generic timestamp mention, so the description does not fully compensate for the gap. Overall it adds modest meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 ... recurring-service events') and names the main filter dimensions, so an agent can tell this is a paginated events-list operation. It routes to memberships_recurring_services_get for the parent record, but does not explicitly contrast this events list with memberships_recurring_services_list, so sibling differentiation is only partial. Still, the core purpose is unmistakable.

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?

It explicitly tells the agent to use memberships_recurring_services_get when it needs the parent service record and job tools when the event references a job, providing useful exclusions. It does not enumerate every alternative or state a precise condition for when this list is preferred, but the guidance is clear enough.

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

Deploy Server