Skip to main content
Glama
montrellcruse

ServiceTitan MCP

by montrellcruse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

crm_bookings_list

Read-onlyIdempotent

Search and filter bookings by ID, external ID, or created/modified date ranges. Retrieve a paginated list of matching records to locate specific bookings.

Instructions

Search tenant bookings by IDs, external ID, or created and modified ranges. Returns one page; use crm_bookings_get for a known booking ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoComma-delimited booking IDs (max 50)
pageNoPage number (starts at 1)
sortNoSort: Field (default), +Field (asc), or -Field (desc). Fields: Id, ModifiedOn, CreatedOn
pageSizeNoRecords per page (default 50)
externalIdNoExternal booking ID
includeTotalNoInclude total count in response
createdBeforeNo
modifiedBeforeNo
createdOnOrAfterNo
modifiedOnOrAfterNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {},
+  "type": "object"
+}
  2. Addedv2.6.2
  3. Removedv2.6.2
  4. First observedv2.5.1

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered. The description adds the real behavioral detail 'Returns one page', which is not visible in annotations and alerts the agent that results are paginated.

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 what the tool searches, the second states the pagination behavior and the key alternative. Every clause adds information an agent needs.

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 paginated search/list tool with rich annotations and an output schema, the description covers the core behavior and the main sibling decision (get vs list). It does not mention other potentially relevant alternatives such as export_bookings, but the schema and annotations fill enough context for correct invocation.

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 coverage is 60%, with the four date-time parameters lacking descriptions; the description's 'created and modified ranges' fills in that gap by grouping them into meaningful filter dimensions. The schema already documents page/pageSize/sort/externalId/includeTotal, and the description's enumeration of search keys adds semantic grouping without repeating the schema.

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: 'Search tenant bookings'. It then enumerates the precise search dimensions (IDs, external ID, created/modified ranges), and explicitly distinguishes itself from crm_bookings_get, so an agent can tell when to use which without opening the schema.

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?

It gives explicit routing guidance: 'use crm_bookings_get for a known booking ID', which is a clear when-not condition. The phrase 'Returns one page' also signals this is a paginated list operation rather than a bulk export, and the filter list defines the primary use case.

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

Deploy Server

Other Tools