Skip to main content
Glama
montrellcruse

ServiceTitan MCP Server (Enterprise)

accounting_invoices_list

Retrieve and filter accounting invoices from ServiceTitan using criteria like status, date ranges, amounts, and customer details to manage billing and payments.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoComma-delimited invoice IDs
statusesNoInvoice statuses
batchIdNoBatch ID
batchNumberNoBatch number
customFieldFieldsNoCustom field name/value filters
customFieldOperatorNoOperator for custom field filters
jobIdNoJob ID
jobNumberNoJob number
businessUnitIdNoBusiness unit ID
customerIdNoCustomer ID
invoicedOnOrAfterNoInvoiced on or after RFC3339 date-time
invoicedOnBeforeNoInvoiced on or before RFC3339 date-time
adjustmentToIdNoAdjusted invoice ID
numberNoInvoice number
totalGreaterNoMinimum invoice total
totalLessNoMaximum invoice total
balanceFilterBalanceNoBalance filter value
balanceFilterComparerNoBalance comparison operator
dueDateBeforeNoDue date before RFC3339 date-time
dueDateOnOrAfterNoDue date on or after RFC3339 date-time
orderByNoOrder by field
orderByDirectionNoOrder direction: asc|desc
reviewStatusesNoReview statuses
assignedToIdsNoAssignee user IDs
sortNoSort: Field (default), +Field (asc), or -Field (desc). Fields: Id, ModifiedOn, CreatedOn, Number, InvoicedOn, DueDate, Total, Balance
createdBeforeNo
createdOnOrAfterNo
modifiedBeforeNo
modifiedOnOrAfterNo
pageNoPage number (starts at 1)
pageSizeNoRecords per page (default 50)
includeTotalNoInclude total count in response
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