Skip to main content
Glama
montrellcruse

ServiceTitan MCP Server (Enterprise)

inventory_purchase_orders_list

Retrieve and filter purchase orders from ServiceTitan inventory by status, date, job, technician, or other criteria to manage procurement workflows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoComma-separated purchase order IDs (maximum 50)
statusNoFilter by purchase order status
numberNoFilter by purchase order number
jobIdNoFilter by job ID
jobIdsNoComma-separated job IDs
technicianIdNoFilter by technician ID
projectIdNoFilter by project ID
dateOnOrAfterNoFilter by purchase order date on or after this value
dateBeforeNoFilter by purchase order date before this value
sentOnOrAfterNoFilter by sent-on date on or after this value
sentBeforeNoFilter by sent-on date before this value
sortNoSort: Field (default), +Field (asc), or -Field (desc). Fields: Id, ModifiedOn, CreatedOn
pageNoPage number (starts at 1)
pageSizeNoRecords per page (default 50)
includeTotalNoInclude total count in response
createdBeforeNo
createdOnOrAfterNo
modifiedBeforeNo
modifiedOnOrAfterNo
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/montrellcruse/servicetitan-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server