Skip to main content
Glama
JordanDalton

ServiceTitan MCP Server

invoices_getlist

Retrieve and filter invoices by IDs, dates, statuses, job details, or custom fields using ServiceTitan MCP Server. Supports pagination, sorting, and advanced querying for efficient invoice management.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
adjustmentToIdNoFormat - int64. When searching for adjustment invoices, this field will search for invoices that are adjustments to the specified invoice ID.
assignedToIdsNoAssignedTo IDs associated with invoices.
balanceFilter.BalanceNoFormat - decimal.
balanceFilter.ComparerNoValues: [Equals, NotEquals, Greater, Less]
batchIdNoFormat - int64. Batch ID associated with invoices.
batchNumberNoFormat - int32. Batch number associated with invoices.
businessUnitIdNoFormat - int64. Business unit ID associated with invoices.
createdBeforeNoFormat - date-time (as date-time in RFC3339). Return items created before certain date/time (in UTC)
createdOnOrAfterNoFormat - date-time (as date-time in RFC3339). Return items created on or after certain date/time (in UTC)
customField.FieldsNoDictionary of name-value pairs
customField.OperatorNoOperator to be used between the name-value pairs. Can be "Or" or "And", default is "And".\ Values: [And, Or]
customerIdNoFormat - int64. Customer ID associated with invoices.
dueDateBeforeNoFormat - date-time (as date-time in RFC3339). Retrieve all invoices with a due date before the input value
dueDateOnOrAfterNoFormat - date-time (as date-time in RFC3339). Retrieve all invoices with a due date on after or equal the input value
idsNoComma-delimited list of invoice IDs.
includeTotalNoWhether total count should be returned
invoicedOnBeforeNoFormat - date-time (as date-time in RFC3339).
invoicedOnOrAfterNoFormat - date-time (as date-time in RFC3339).
jobIdNoFormat - int64. Job ID associated with invoices. This will be null if the invoice is not linked to a job.
jobNumberNoJob number associated with invoices. This will be null if the invoice is not linked to a job.
modifiedBeforeNoFormat - date-time (as date-time in RFC3339). Return items modified before certain date/time (in UTC)
modifiedOnOrAfterNoFormat - date-time (as date-time in RFC3339). Return items modified on or after certain date/time (in UTC)
numberNoReference number associated with invoices.
orderByNoField on which you want to order the returned list of invoices.
orderByDirectionNoOrder direction of the retuned list of invoices. Values of "desc" or "descending" will order the list in descending order, otherwise the list will be ordered in ascending order.
pageNoFormat - int32. The logical number of page to return, starting from 1
pageSizeNoFormat - int32. How many records to return (50 by default)
reviewStatusesNoReview statuses associated with invoices.
sortNoApplies sorting by the specified field: "?sort=+FieldName" for ascending order, "?sort=-FieldName" for descending order.'
statusesNoTransaction status, which can be one of: Pending, Posted, Exported. By default, all transaction statuses are included. If you want to filter by more than one status, add a new "statuses" query parameter for each status you want to include. For example: &statuses=Pending&statuses=Posted
tenantYesFormat - int64. Tenant ID
totalGreaterNoFormat - decimal. Retrieve all invoices with a total greater than or equal to the input value.
totalLessNoFormat - decimal. Retrieve all invoices with a total less than or equal to the input value.
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/JordanDalton/ServiceTitanMcpServer'

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