ServiceTitan MCP

inventory_purchase_orders_list

Read-onlyIdempotent

Retrieve a page of issued purchase orders filtered by IDs, number, status, technician, job, project, or date. Get only the records you need for review or reconciliation.

Instructions

List one requested page of issued purchase orders using IDs, number, status, technician, job, project, and order or sent-date filters. Use inventory_purchase_orders_get for one known order and inventory_purchase_orders_requests_list for requests that precede issued orders.

Input Schema

TableJSON Schema

Name	Required	Description
`ids`	No	Comma-separated purchase order IDs (maximum 50)
`page`	No	Page number (starts at 1)
`sort`	No	Sort: Field (default), +Field (asc), or -Field (desc). Fields: Id, ModifiedOn, CreatedOn
`jobId`	No	Filter by job ID
`jobIds`	No	Comma-separated job IDs
`number`	No	Filter by purchase order number
`status`	No	Filter by purchase order status
`pageSize`	No	Records per page (default 50)
`projectId`	No	Filter by project ID
`dateBefore`	No	Filter by purchase order date before this value
`sentBefore`	No	Filter by sent-on date before this value
`includeTotal`	No	Include total count in response
`technicianId`	No	Filter by technician ID
`createdBefore`	No
`dateOnOrAfter`	No	Filter by purchase order date on or after this value
`sentOnOrAfter`	No	Filter by sent-on date on or after this value
`modifiedBefore`	No
`createdOnOrAfter`	No
`modifiedOnOrAfter`	No

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

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds useful behavioral context beyond those: it returns a single requested page and focuses specifically on issued purchase orders rather than requests. It does not deeply discuss result limits or response shape, but output schema covers that.

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 tight sentences with no filler. The core function and filter scope come first, and sibling routing comes second. Every phrase 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 19-parameter list tool with an output schema and strong annotations, the description is complete enough for correct selection: it states pagination, filter scope, and the main sibling distinctions. It could be slightly more precise about created/modified filters or the meaning of 'issued,' but the schema and sibling names fill most gaps.

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?

The schema covers most parameter descriptions, so the baseline is solid. The description adds semantic grouping by naming the filter dimensions ('IDs, number, status, technician, job, project, and order or sent-date filters') and clarifies that date filters split into order-date and sent-date. It does not mention created/modified filters, but the schema already documents those reasonably.

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 ('List'), a clear resource ('issued purchase orders'), and states the scope ('one requested page') plus the available filter dimensions. It clearly distinguishes itself from inventory_purchase_orders_get and inventory_purchase_orders_requests_list, which are the closest siblings.

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 tells the agent when to use this tool versus alternatives: use inventory_purchase_orders_get for one known order and inventory_purchase_orders_requests_list for requests preceding issued orders. This is direct, actionable routing guidance.

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

Deploy Server