ServiceTitan MCP

dispatch_images_get

Read-onlyIdempotent

Retrieve image response data from ServiceTitan using a known storage path. Use this tool to fetch image content directly; discover job attachment paths first via job attachment listing.

Instructions

Request image response data for a ServiceTitan storage path. The upstream Pricebook image operation documents an HTTP 302 redirect; this wrapper returns the client-decoded response body through its standard JSON/text envelope, without exposing the redirect Location header. Supply the known path when targeting an image; use dispatch_jobs_list_attachments to discover job attachments.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`path`	No	Storage path of the image to retrieve

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.4/5.0

Behavior4/5

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

The annotations already cover read-only/idempotent/non-destructive, and the description adds meaningful behavior beyond that: the upstream HTTP 302 redirect is followed, the Location header is not exposed, and the response is returned through a standard JSON/text envelope. This is useful operational context, though 'standard envelope' is left somewhat generic.

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?

Three sentences, each earning its place: purpose, redirect/envelope behavior, and sibling routing. The most decision-relevant information is front-loaded.

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

Completeness4/5

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

For a one-parameter read operation with an output schema and rich annotations, the description covers the operation's purpose, behavior, and how to discover valid paths. It is slightly generic about where 'known path' values originate beyond job attachments, but enough context is provided for an agent to invoke it correctly.

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

Parameters3/5

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

Schema coverage is 100% for the single path parameter, so the schema already documents it. The description reinforces that a known path should be supplied when targeting an image, but it doesn't add format, encoding, or error details; with complete schema coverage this meets the baseline without adding extra nuance.

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 identifies the specific operation ('Request image response data for a ServiceTitan storage path') and the wrapper's decoded-envelope behavior, and distinguishes it from dispatch_jobs_list_attachments. An agent can determine what this tool does without opening the schema.

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?

It states when to use the tool ('Supply the known path when targeting an image') and explicitly directs agents to dispatch_jobs_list_attachments when discovery of job attachments is needed. This gives clear routing among the large sibling set.

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

Deploy Server