ServiceTitan MCP

inventory_vendors_list

Read-onlyIdempotent

List inventory vendors page by page with filters for IDs, active status, created or modified timestamps, and external-data mapping to locate vendors matching your criteria.

Instructions

List one requested page of inventory vendors using IDs, active state, created or modified timestamps, and external-data mapping filters. Use inventory_vendors_get for one known vendor; use inventory_purchase_orders_list for purchase-order records.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ids`	No	Collection of vendor IDs to filter by
`page`	No	Page number (starts at 1)
`sort`	No	Sort: Field (default), +Field (asc), or -Field (desc). Fields: Id, ModifiedOn, CreatedOn
`active`	No	Filter by active status	True
`pageSize`	No	Records per page (default 50)
`includeTotal`	No	Include total count in response
`createdBefore`	No
`modifiedBefore`	No
`externalDataKey`	No	External data key used with externalDataValues
`createdOnOrAfter`	No
`modifiedOnOrAfter`	No
`externalDataValues`	No	External data values used with externalDataKey
`externalDataApplicationGuid`	No	External data application GUID for lookup

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

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safe-read nature is covered. The description adds behavioral context by clarifying that the tool returns a single requested page rather than all vendors, and it summarizes the filter groups. It does not contradict any annotation.

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 two sentences with no wasted words. The first sentence front-loads the action, resource, pagination, and filter categories; the second sentence provides alternative routing. It earns its place entirely.

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?

For a read-only list endpoint with an output schema, rich annotations, and 13 well-schemaed parameters, the description is sufficient. It covers the essential behavioral point (one page), lists filter categories, and disambiguates from sibling tools. Remaining details like defaults and sorting are already present in the input schema.

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 69%, and the description adds value by grouping parameters into meaningful categories: IDs, active state, created/modified timestamps, and external-data mapping. This is especially helpful for the four date-time parameters that lack individual schema descriptions. Page, pageSize, and sort are well-documented in the schema, so the description does not need to repeat them.

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 states a specific action and resource: 'List one requested page of inventory vendors' and names the filter dimensions. It also distinguishes itself from inventory_vendors_get (single known vendor) and inventory_purchase_orders_list (purchase-order records), leaving no ambiguity about what this tool does.

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?

The description explicitly tells the agent when to use alternatives: 'Use inventory_vendors_get for one known vendor; use inventory_purchase_orders_list for purchase-order records.' This is direct routing guidance that helps the agent pick the right tool among related inventory endpoints.

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

Deploy Server