ServiceTitan MCP

dispatch_form_submissions_list

Read-onlyIdempotent

Search submitted form records using filters like form, status, owner, creator, and submission date to retrieve paginated results.

Instructions

Search submitted form records by form, creator, status, owner expression, submitted range, or active state. Returns one page; use this for submission results rather than form definitions.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No	Page number (starts at 1)
`sort`	No	Sort: Field (default), +Field (asc), or -Field (desc). Fields: Id, SubmittedOn, CreatedBy
`active`	No	Filter by active status	True
`owners`	No	Owner query expression used by ServiceTitan submissions endpoint
`status`	No	Submission status filter
`formIds`	No	Comma-separated form IDs
`pageSize`	No	Records per page (default 50)
`ownerType`	No	Owner type filter
`createdById`	No	Creator user ID
`includeTotal`	No	Include total count in response
`submittedBefore`	No	Return submissions submitted before this UTC timestamp
`submittedOnOrAfter`	No	Return submissions submitted on or after this UTC 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.0

Behavior3/5

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

Annotations already carry the safety profile (readOnlyHint=true, destructiveHint=false, idempotentHint=true). The description adds one useful behavioral fact: 'Returns one page'. It does not disclose additional behavioral details like default active filtering or pagination semantics, but those are covered by the schema. No contradiction 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 sentences, front-loaded with the action and resource, followed by a useful pagination note and a clear differentiation from form definitions. Every sentence earns its place with no redundancy.

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 12-parameter read-only list tool with full schema coverage and an output schema, the description is adequately complete: it names the entity, the filter families, the one-page behavior, and the key distinction from form definitions. It could mention the exact sibling for form definitions or pagination strategy, but these are not critical gaps given the schema and annotations.

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 100%, so the baseline is 3. The description summarizes the main filter categories (form, creator, status, owner expression, submitted range, active state), which maps to the schema parameters, but it adds no syntax, defaults, or relationship details beyond what the schema already documents.

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 submitted form records', and lists concrete filter dimensions (form, creator, status, owner expression, submitted range, active state). It also distinguishes this tool from form-definition tools by stating 'use this for submission results rather than form definitions', matching the sibling dispatch_forms_list.

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 usage context: it is for submission results, not form definitions. It could name the alternative tool explicitly (e.g., dispatch_forms_list), but the conceptual exclusion is enough for an agent to orient itself among the siblings.

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

Deploy Server