Skip to main content
Glama
montrellcruse

ServiceTitan MCP

by montrellcruse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

export_calls

Read-onlyIdempotent

Pull incremental call records in bulk for synchronization. Start from a date or feed beginning, continue with tokens while more data exists, and use recent changes for quicker updates while handling repeats.

Instructions

Read the incremental calls export feed for bulk synchronization. Start with a date or omit from to start at the beginning of the feed, continue immediately with continueFrom while hasMore is true, and when false retain it and wait before polling again. includeRecentChanges may return records sooner but can repeat them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromNoContinuation token or date string for incremental export
includeRecentChangesNoInclude recent changes not yet committed

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. First observedv2.5.1

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint, idempotentHint, and openWorldHint annotations, the description discloses the incremental feed behavior: continuation via continueFrom, the hasMore loop, waiting before polling again, and the potential for duplicate records with includeRecentChanges. This adds meaningful behavioral detail not present in the 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?

The description is compact, front-loaded with the core purpose, and each sentence contributes actionable guidance about the pagination and polling flow. There is no redundant or filler content.

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?

Given the presence of a rich output schema, annotations covering safety/idempotency, and only two parameters, the description provides sufficient guidance for an agent to invoke the tool correctly and understand the incremental export lifecycle, including continuation and polling behavior.

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 100%, so the schema already documents both parameters. The description adds value by explaining that 'from' can be a date or omitted to start at the beginning, and that includeRecentChanges may return records sooner but can repeat them, which goes beyond the schema descriptions.

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 states a specific verb and resource: 'Read the incremental calls export feed for bulk synchronization.' It clearly identifies the tool's purpose, though it does not explicitly differentiate itself from the many sibling export_* tools beyond the resource name.

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 clear operational context for bulk synchronization and explains the starting point ('Start with a date or omit from'). It does not explicitly mention alternatives or when-not-to-use, but the usage pattern is specific enough to guide an agent.

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