Skip to main content
Glama
JordanDalton

ServiceTitan MCP Server

GlAccounts_GetList

Retrieve a list of GL accounts by specifying filters like IDs, names, types, activity status, or creation/modification dates. Supports pagination and sorting for efficient account management within ServiceTitan.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
activeNoSpecify if only active accounts, only inactive accounts, or both, should be retrieved. By default, only active accounts will be retrieved. Values: [True, Any, False]
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)
descriptionNoA substring that must be contained in the account description
idsNoComma-delimited list of account IDs, maximum 50 items
includeTotalNoWhether total count should be returned
isIntacctBankAccountNoSet to true to retrieve Intacct bank accounts only
isIntacctGroupNoSet to true to retrieve Intacct group accounts only
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)
namesNoComma-delimited list of account names, maximum 50 items
numbersNoComma-delimited list of account numbers, maximum 50 items
pageNoFormat - int32. The logical number of page to return, starting from 1
pageSizeNoFormat - int32. How many records to return (50 by default)
sortNoApplies sorting by specified fields
sourceNoAccount source Values: [Undefined, AccountingSystem, ManuallyCreated, PublicApi]
subtypesNoComma-delimited list of account subtypes, maximum 50 items
tenantYesFormat - int64. Tenant ID
typesNoComma-delimited list of account types, maximum 50 items
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