ServiceTitan MCP

memberships_list

Read-onlyIdempotent

Returns a page of customer membership records filtered by customer/membership IDs, status, active state, billing frequency, duration, and timestamps. Use for searching or auditing sold memberships.

Instructions

List one requested page of customer membership records using membership and customer IDs, status, active state, billing frequency, duration, and created or modified timestamps. Use memberships_get for one known sold membership and memberships_types_list for reusable membership-plan definitions.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ids`	No	Comma-separated membership IDs (maximum 50)
`page`	No	Page number (starts at 1)
`active`	No	Filter by active status	True
`status`	No	Filter by membership status
`duration`	No	Filter by membership duration in months
`pageSize`	No	Records per page (default 50)
`customerIds`	No	Comma-separated customer IDs
`includeTotal`	No	Include total count in response
`createdBefore`	No
`modifiedBefore`	No
`billingFrequency`	No	Filter by membership billing frequency
`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

Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the read-only safety profile is covered. The description adds only the 'one requested page' pagination trait and the customer-membership scope, which is useful but not rich behavioral context like defaults, response limits, or completeness behavior.

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 first states the action and filter dimensions, the second routes to the two most relevant alternatives. Every clause earns its place, and the core behavior is front-loaded.

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?

Given an output schema, 13 optional parameters, and strong annotations, the description is largely complete: it defines the resource scope, the paginated nature, and sibling routing. Minor gaps such as not mentioning defaults or the bulk export alternative are not critical because the schema and sibling list provide that context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 69%, so the description partly compensates by grouping the filter surface: membership and customer IDs, status, active state, billing frequency, duration, and created/modified timestamps. This is particularly helpful for the four datetime parameters, which lack individual schema descriptions, and gives agents a concise map of the query dimensions.

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-resource pair: 'List one requested page of customer membership records,' and enumerates the available filter dimensions. It also explicitly differentiates itself from memberships_get (one known sold membership) and memberships_types_list (reusable membership-plan definitions), so an agent can distinguish it from nearby siblings.

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 gives direct routing guidance: use memberships_get when you need one known sold membership, and memberships_types_list for reusable plan definitions. This is an explicit when-to-use-alternatives statement, leaving little room for ambiguity about which tool to select.

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

Deploy Server