ServiceTitan MCP

marketing_attributed_leads_get

Read-onlyIdempotent

Retrieve marketing-attributed leads within a UTC time window, optionally filtered by lead type, with paginated results and total count.

Instructions

Search attributed leads within a required UTC time window, optionally filtered by lead type. Returns one page of leads linked to marketing attribution activity.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number (starts at 1)
`toUtc`	Yes	End date/time in UTC for the filtering period
`fromUtc`	Yes	Start date/time in UTC for the filtering period
`leadType`	No	Lead type filter
`pageSize`	No	Records per page (default 50)
`includeTotal`	No	Include total count in response

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.2/5.0

Behavior4/5

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

Annotations already carry the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the bar is lower. The description adds value beyond them by disclosing pagination behavior ('Returns one page') and that the result set is specifically attribution-linked, which complements openWorldHint rather than contradicting it.

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 zero filler; the core action and mandatory constraint are front-loaded, followed by the optional filter and the return behavior. Every sentence earns its place.

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 6-parameter search tool with a full output schema, the description covers the essentials: required window, optional filter, and paged response. Minor gaps remain—no guidance on default page size or what 'attributed' means exactly—but the schema documents defaults and the output schema renders return-value explanation unnecessary.

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 baseline is 3. The description adds real semantic value on top by flagging which parameters actually matter: the UTC time window is required and leadType is optional, and 'one page' orients the paging parameters (page, pageSize). This helps an agent decide parameter usage without digging into 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 uses a specific verb ('Search') with a clearly scoped resource ('attributed leads') and immediately states the two defining constraints: a required UTC time window and an optional lead-type filter. The closing phrase 'linked to marketing attribution activity' distinguishes this from generic lead tools among the siblings (crm_leads_list, export_leads) and from the other marketing_* tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is implied rather than stated: an agent can infer this is the tool for time-window-based searches of attributed leads, and the mention of paging signals it returns one page rather than a bulk export. However, it never names an alternative (e.g., export_leads, crm_leads_list, marketing_calls_*) or states when not to use it, leaving routing to inference in a sibling list of 200+ tools.

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

Deploy Server