Skip to main content
Glama
JordanDalton

ServiceTitan MCP Server

journal_entries_get_list

Retrieve a list of journal entries from ServiceTitan based on filters like IDs, dates, statuses, or custom fields. Supports sorting, pagination, and filtering by transactions, customers, vendors, or business units.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
businessUnitIdsNoComma-delimited list of business unit IDs, maximum 50 items
createdBeforeNoReturn items created before certain date/time (in UTC)
createdOnOrAfterNoReturn items created on or after certain date/time (in UTC)
customFieldNoFilter by custom fields associated with journal entries. Example: ?customField.fieldName1=value1&customField.fieldName2=value2. A field with null value, and a non-existent field are treated equally. Maximum 5 custom fields are supported in one request.
customerNameNoContains a transaction for a customer with name containing
exportedByNoComma-delimited list of user IDs, maximum 50 items
exportedFromNoExported on or after certain date/time (in UTC)
exportedToNoExported on or before certain date/time (in UTC)
idsNoComma-delimited list of journal entry IDs, maximum 50 items
includeTotalNoWhether total count should be returned
inventoryLocationNameNoContains a transaction for an inventory location with name containing
locationNameNoContains a transaction for a customer location with name containing
modifiedBeforeNoReturn items modified before certain date/time (in UTC)
modifiedOnOrAfterNoReturn items modified on or after certain date/time (in UTC)
nameNoName contains
numberFromNoNumber is greater or equal than
numberToNoNumber is less or equal to
pageNoThe logical number of page to return, starting from 1
pageSizeNoHow many records to return (50 by default). Maximum value is 500.
postedFromNoPosted on or after certain date/time (in UTC)
postedToNoPosted on or before certain date/time (in UTC)
refNumberNoContains a transaction with reference number containing
serviceAgreementIdsNoComma-delimited list of service agreement IDs, maximum 50 items
sortNoApplies sorting by the specified field and direction. Options: Id, Number, Name, Status, CreatedOn, ExportedOn, ExportedBy, PostDate. Use "+" for ascending order, and "-" for descending order. Example: "?sort=-Number" will sort by number in descending order.
statusesNoArray of statuses
syncStatusesNoArray of sync statuses
tenantYesTenant ID
transactionPostedFromNoContains a transaction posted on or after certain date/time (in UTC)
transactionPostedToNoContains a transaction posted on or before certain date/time (in UTC)
transactionTypesNoList of transaction types. A journal entry will be returned if it contains at least one transaction of this type.
vendorNameNoContains a transaction for a vendor with name containing
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