Skip to main content
Glama
montrellcruse

ServiceTitan MCP

by montrellcruse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

crm_customers_notes_list

Read-onlyIdempotent

Retrieve customer notes using the customer ID, with optional date filters to find notes created or modified within a specific timeframe.

Instructions

List one page of notes attached to a known customer, optionally filtered by created or modified timestamps. Requires the customer ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCustomer ID
pageNoPage number (starts at 1)
pageSizeNoRecords per page (default 50)
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.2/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds operational context beyond that: results are paginated ('one page') and can be filtered by created/modified timestamps, plus the hard precondition of a customer ID. No contradictions with annotations.

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 short sentences with no filler. The core action and scope are front-loaded, followed by the optional filters and the prerequisite. Every clause contributes useful information.

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?

With an output schema present, return-value documentation is not needed. The description covers the essential calling context: pagination, timestamp filtering, and the required customer ID. Minor gaps such as default page size and exact filter parameter names are already present in the input schema, so nothing critical 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 only 50%, leaving the four timestamp parameters undocumented. The description partially compensates by explaining they filter by 'created or modified timestamps' and that the ID is required, but it does not elaborate on before/on-or-after semantics or pagination defaults beyond what the schema already names.

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 names a specific verb ('List'), a specific resource ('notes attached to a known customer'), and the key scoping detail ('one page', 'Requires the customer ID'). It clearly distinguishes this from other list tools by tying it to customer notes, even among many sibling note-list tools.

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?

The description gives a clear prerequisite ('Requires the customer ID') and implies this is for fetching a paginated set of notes for a known customer, not a broad export or a different entity's notes. It does not explicitly name alternative tools for locations/leads/jobs notes, but the customer-specific wording makes the intended context reasonably clear.

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