ServiceTitan MCP

marketing_scheduler_scheduler_performance

Read-onlyIdempotent

Retrieve a scheduler's performance metrics over a custom session-created time window. Provides the summary response for the specified scheduler ID and date range.

Instructions

Retrieve one scheduler's performance metrics over a required session-created time window. Returns the scheduler performance response for that exact ID and period; use marketing_scheduler_schedulersessions for individual sessions.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Scheduler ID
`sessionCreatedBefore`	Yes	Session created before timestamp
`sessionCreatedOnOrAfter`	Yes	Session created on or after timestamp

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

Behavior3/5

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

The annotations already declare read-only, idempotent, non-destructive behavior, so the description only needs to add context beyond that. It adds the exact-ID/period scoping, but doesn't describe response shape or edge cases; output schema covers response shape, so this is acceptable but not highly informative.

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 tightly written sentences front-load the action and resource, then add the disambiguation to a sibling. No filler or repetition of schema details.

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?

Annotations cover safety/idempotence, output schema covers the return payload, and the description covers scope and the key sibling distinction. Nothing else is needed to select and invoke this tool correctly.

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%, giving baseline 3. The description adds value by framing the two date fields as a required 'session-created time window' and reinforcing that the id must exactly identify the scheduler, which helps an agent understand the relationship between parameters.

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 ('Retrieve'), a precise resource ('one scheduler's performance metrics'), and a required temporal scope ('session-created time window'). It also distinguishes itself from marketing_scheduler_schedulersessions by noting that sibling handles individual sessions.

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 explicitly names marketing_scheduler_schedulersessions as the tool for individual sessions, which tells an agent when not to choose this tool. The 'exact ID and period' phrasing also clarifies that this tool is for a single scheduler's aggregate metrics.

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

Deploy Server