ServiceTitan MCP

accounting_gl_accounts_get

Read-onlyIdempotent

Retrieve a specific GL account by its ServiceTitan ID. Returns the exact upstream record without pagination; use list search when the ID is unknown.

Instructions

Retrieve a GL account by its ServiceTitan ID. Returns the single upstream record without pagination; use accounting_gl_accounts_list to search when the ID is unknown.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`accountId`	Yes	GL account ID

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv3.0.0Sep 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {},
+  "type": "object"
+}

First observedv2.5.1Apr 18, 2026

TDQS

A4.7/5.0

Behavior4/5

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

The annotations already declare the tool read-only and idempotent, so the description does not need to repeat those safe behaviors. The added note that it returns a single upstream record without pagination is genuine behavioral context that helps the agent understand response scope and avoid expecting pagination.

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

Conciseness5/5

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

Two sentences with no filler. The primary behavior is front-loaded, and the alternative-tool guidance is compactly appended. Every sentence carries meaningful information.

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

Completeness5/5

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

This is a simple single-parameter get-by-ID operation with a full output schema and safety annotations. The description covers the core behavior, absence of pagination, and the relevant alternative for unknown IDs, leaving no material gap for correct invocation.

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

Parameters4/5

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

The input schema already documents accountId as a required integer 'GL account ID', and coverage is 100%. The description adds value by clarifying that this is the ServiceTitan ID, which reinforces the external identifier semantics and connects the parameter to the tool's stated purpose.

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

Purpose5/5

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

The description uses a specific verb ('Retrieve') with a clear resource ('a GL account by its ServiceTitan ID') and explicitly contrasts this tool with accounting_gl_accounts_list. The distinction between a direct fetch by ID and a search list is unambiguous, so an agent can tell them apart immediately.

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

Usage Guidelines5/5

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

The description states exactly when to use this tool—when the ServiceTitan ID is known—and explicitly names accounting_gl_accounts_list as the alternative when the ID is unknown. This gives the agent a clear decision rule with no inference required.

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

Deploy Server