ServiceTitan MCP

memberships_service_agreements_list

Read-onlyIdempotent

List customer service agreements with filters for customer, status, business unit, and date ranges. Get a specific page of records to review or manage agreement data.

Instructions

List one requested page of customer service agreements using agreement, customer, business-unit, status, and created or modified timestamp filters. Use memberships_service_agreements_get for a known agreement; use memberships_list for customer membership sales rather than agreement records.

Input Schema

TableJSON Schema

Name	Required	Description
`ids`	No	Comma-separated service agreement IDs (maximum 50)
`page`	No	Page number (starts at 1)
`sort`	No	Sort: Field (default), +Field (asc), or -Field (desc). Fields: Id, Name, CreatedOn, ModifiedOn, StartDate, EndDate
`status`	No	Filter by service agreement status
`pageSize`	No	Records per page (default 50)
`customerIds`	No	Comma-separated customer IDs
`includeTotal`	No	Include total count in response
`createdBefore`	No
`modifiedBefore`	No
`businessUnitIds`	No	Comma-separated business unit IDs
`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/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds useful behavioral context beyond these annotations: it returns 'one requested page' and enumerates the available filter dimensions, which helps set caller expectations for pagination and filtering.

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 behavior and pagination scope are front-loaded, and the alternative-tool routing is placed second. Every sentence 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?

For a read-only, idempotent list tool with an output schema and annotations covering safety, the description is complete: it states the resource, paging behavior, filtering options, and sibling-tool boundary. No critical invocation information is missing.

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 67%, so the schema documents most parameters. The description adds a useful high-level grouping of filters (agreement, customer, business-unit, status, timestamp) but does not add detail beyond what the schema already provides, and the four timestamp parameters remain schematically undocumented.

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 and resource: 'List one requested page of customer service agreements.' It also names the sibling tools it is not (memberships_service_agreements_get and memberships_list), making the tool's scope distinguishable without inspecting schemas.

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 says to use memberships_service_agreements_get when a known agreement is needed and memberships_list for customer membership sales 'rather than agreement records.' This gives clear routing guidance and an explicit exclusion, so an agent knows when not to choose this tool.

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

Deploy Server